All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: LOPEZ Jean-Charles <jelopez@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Ceph stable releases and backports team
Date: Fri, 17 Apr 2015 10:50:35 +0200	[thread overview]
Message-ID: <5530C95B.2020008@dachary.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]

Hi Jean-Charles,

During our phone conversation earlier this week you said that it was not clear what is expected of you as a team member. In addition to the explanations I gave you  I tried to write that down in the HOWTO:

http://tracker.ceph.com/projects/ceph-releases/wiki/HOWTO#Organize-the-stable-releases-and-backports-team

It still is a little fuzzy but I think what we want eventually is that each of us is responsible for the advancement of the next point release for a given stable branch. It shows by assigning issues as can be viewed at http://tracker.ceph.com/projects/ceph-releases/issues

Dumpling Alistair Israel
Firefly Xinxin Shu
Giant Abhishek Lekshmanan
Hammer Jean-Charles Lopez

Ideally there would be two team member per release, in case one of them is on vacation or something. However, since we're still polishing the process, I'll act as a backup. Ideally you would just have to tell me: here, the issue http://tracker.ceph.com/issues/11353 is yours, all the information you need to take over is in it.

Cheers

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

                 reply	other threads:[~2015-04-17  8:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5530C95B.2020008@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=jelopez@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.