From: Loic Dachary <loic@dachary.org>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: dumpling branch for v0.67.12 is ready for release
Date: Tue, 24 Feb 2015 18:10:06 +0100 [thread overview]
Message-ID: <54ECB06E.9020507@dachary.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 835 bytes --]
Hi Sage,
QE approved https://github.com/ceph/ceph/commit/77dfbbaccfb5074899d02314a26cb9ac46a69106 for release in the https://github.com/ceph/ceph/commits/dumpling branch. The release notes should now be written based on the content of the issues and pull requests mentioned here http://workbench.dachary.org/ceph/ceph-backports/wikis/dumpling#already-merged
The release notes can now be written. In the future I'll ask about the release notes earlier: the last tests do not change anything significant and take days if not week. They can conveniently be done while the release notes are written[1] instead of making them a blocker at the very end.
Cheers
[1] Cutting a new stable release http://ceph.com/docs/master/dev/development-workflow/#cutting-a-new-stable-release
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2015-02-24 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 17:10 Loic Dachary [this message]
2015-03-15 21:24 ` dumpling branch for v0.67.12 is ready for release 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=54ECB06E.9020507@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
/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.