From: Loic Dachary <loic@dachary.org>
To: Abhishek L <abhishek.lekshmanan@gmail.com>,
Abhishek Varshney <abhishek.varshney@flipkart.com>,
Nathan Cutler <ncutler@suse.cz>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: hammer v0.94.7 & jewel
Date: Mon, 8 Feb 2016 14:13:50 +0700 [thread overview]
Message-ID: <56B8402E.60402@dachary.org> (raw)
Dear backporters,
Hammer v0.94.6 will be published soon and now would be a good time to start v0.94.7. I'm willing to participate in this release, either as backup or driver. If you'd like to help as well, feel free to update http://tracker.ceph.com/projects/ceph-releases/wiki/HOWTO#Whos-who with the role that you prefer. The past few weeks have been good (much better than when the make check bot was down and the test infrastructure in construction, that's for sure ;-). Even at normal priority the tests take less than a week to complete and often less than 48h, which is really confortable. And since we now all have access to the lab, there is nothing stopping progress!
In a few weeks jewel will be published and we'll have one more stable release to care for. Maybe we could send a call for participation to get more help ? One or two mentee when the work starts on v0.94.7 would be ideal. It turns out that Robin had no time for learning the process on v0.94.6 (although he did numerous patches to improve teuthology and therefore helped with backports in other ways). And since Firefly is EOL, Swami did not get a chance either. This is not to say we're in a bad position, but I think it's an additional incentive to recruit now.
What do you think ?
Cheers
--
Loïc Dachary, Artisan Logiciel Libre
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2016-02-08 7:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 7:13 Loic Dachary [this message]
2016-02-08 8:35 ` hammer v0.94.7 & jewel M Ranga Swami Reddy
2016-02-08 8:54 ` Loic Dachary
2016-02-08 9:23 ` Nathan Cutler
2016-02-08 10:42 ` 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=56B8402E.60402@dachary.org \
--to=loic@dachary.org \
--cc=abhishek.lekshmanan@gmail.com \
--cc=abhishek.varshney@flipkart.com \
--cc=ceph-devel@vger.kernel.org \
--cc=ncutler@suse.cz \
/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.