From: Loic Dachary <loic@dachary.org>
To: Abhishek L <abhishek.lekshmanan@gmail.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Upcoming 10.2.4
Date: Mon, 10 Oct 2016 12:59:32 +0200 [thread overview]
Message-ID: <57FB7494.1010309@dachary.org> (raw)
Hi Abhishek,
Since you're now release manager, it is my understanding that we'll be asking you if the release should be cut or not. I updated the issue tracking the progress of 10.2.4 accordingly. This is a heads up to let you know we'll most likely ask that question for 10.2.4 some time next week ;-)
Cheers
[1] http://tracker.ceph.com/journals/diff/79457?detail_id=76318
--
Loïc Dachary, Artisan Logiciel Libre
next reply other threads:[~2016-10-10 10:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 10:59 Loic Dachary [this message]
2016-10-11 10:15 ` Upcoming 10.2.4 John Spray
2016-10-11 10:33 ` Dan van der Ster
2016-10-11 10:48 ` Loic Dachary
2016-10-11 10:36 ` Loic Dachary
2016-10-11 16:59 ` Ken Dreyer
2016-10-11 17:35 ` Loic Dachary
2016-10-11 18:38 ` Orit Wasserman
2016-10-11 18:48 ` Loic Dachary
2016-10-19 9:52 ` Loic Dachary
2016-10-19 14:26 ` Jason Dillaman
2016-10-19 14:54 ` 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=57FB7494.1010309@dachary.org \
--to=loic@dachary.org \
--cc=abhishek.lekshmanan@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).