From: Loic Dachary <loic@dachary.org>
To: Alistair Israel <aisrael@gmail.com>,
LOPEZ Jean-Charles <jelopez@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Keeping up with the backports
Date: Thu, 19 Mar 2015 15:44:41 +0100 [thread overview]
Message-ID: <550AE0D9.8080107@dachary.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]
Hi Alistair & Jean-Charles,
Thanks a lot for volunteering to work on the backports !
I have good news: the backlog of backports is almost empty. New backports are being added every day and we are going to make sure they are handled on a weekly basis so that point releases can be published every month or so, if needed. To start small and learn as we make progress, I propose to mentor you on a given point release, starting with cherry-picking backports and preparing an integration branch as described at http://tracker.ceph.com/projects/ceph-releases/wiki/Wiki (which is linked from the http://tracker.ceph.com/projects/ceph-releases/ landing page). The idea is that once you feel confortable you can keep going on your own.
If you agree we can arrange an IRC meeting next week to bootstrap that. Since we have multiple stable releases in flight at any given time, it can conveniently be parallelized. If that's ok with you, Alistair could start with Firefly and Jean-Charles with Dumpling.
Please let me know if you have any question :-)
Cheers
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2015-03-19 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 14:44 Loic Dachary [this message]
[not found] ` <CABYiri8cCavc0LqG8OAb_Obxpr51nKnwXTaLhwX639vUXECurQ@mail.gmail.com>
2015-03-19 15:44 ` Keeping up with the backports Loic Dachary
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=550AE0D9.8080107@dachary.org \
--to=loic@dachary.org \
--cc=aisrael@gmail.com \
--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.