From: Loic Dachary <loic@dachary.org>
To: Sage Weil <sweil@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>,
"Shu, Xinxin" <xinxin.shu@intel.com>
Subject: should we prepare to release firefly v0.80.10 ?
Date: Tue, 21 Apr 2015 12:12:09 +0200 [thread overview]
Message-ID: <55362279.5060105@dachary.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 648 bytes --]
Hi Sage,
The firefly branch has a number of fixes ( http://tracker.ceph.com/issues/11090#Release-information ) and has been used for upgrade tests in the past few weeks. A few other issues have been backported since and are being tested in the integration branch ( http://tracker.ceph.com/issues/11090#teuthology-run-commitb91bbb434e6363a99a632cf3841f70f1f2549f79-integration-branch-april-2015 ).
Do you think these changes deserve a firefly v0.80.10 release ? Should we ask each lead for their approval ? Or is it better to keep backporting what needs to be and wait a few weeks ?
Cheers
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2015-04-21 10:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 10:12 Loic Dachary [this message]
2015-04-21 15:52 ` should we prepare to release firefly v0.80.10 ? Sage Weil
2015-04-21 16:45 ` David Zafman
[not found] ` <acaeb07b-41c3-40bc-87a3-9d82ce346ae7@redhat.com>
[not found] ` <5537229F.4050501@redhat.com>
2015-04-22 8:26 ` Loic Dachary
2015-05-05 9:17 ` Loic Dachary
2015-05-05 18:58 ` David Zafman
2015-05-05 19:04 ` Loic Dachary
2015-05-05 19:24 ` David Zafman
2015-05-15 13:44 ` Loic Dachary
2015-05-15 19:05 ` Sage Weil
2015-05-15 20:19 ` Loic Dachary
2015-05-18 12:47 ` Loic Dachary
2015-05-22 10:43 ` Loic Dachary
2015-05-22 17:34 ` Sage Weil
2015-05-05 9:25 ` 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=55362279.5060105@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=sweil@redhat.com \
--cc=xinxin.shu@intel.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.