From: Mykola Golub <mgolub@mirantis.com>
To: Loic Dachary <loic@dachary.org>
Cc: Sage Weil <sweil@redhat.com>,
Ceph Development <ceph-devel@vger.kernel.org>,
Abhishek Varshney <abhishek.varshney@flipkart.com>
Subject: Re: releasing jewel v10.2.3 ?
Date: Fri, 19 Aug 2016 16:05:30 +0300 [thread overview]
Message-ID: <20160819130529.GC17630@gmail.com> (raw)
In-Reply-To: <57B698D0.1050409@dachary.org>
Loic,
I think this regression is highly desirable to be merged to jewel
before the release:
http://tracker.ceph.com/issues/16654
I have just merged Jason's PR to master.
On Fri, Aug 19, 2016 at 07:27:44AM +0200, Loic Dachary wrote:
> Hi Sage,
>
> Here are the issues that would be in jewel v10.2.3 if we decided to release it now: http://tracker.ceph.com/versions/518
> And here is the backport queue : http://tracker.ceph.com/projects/ceph/issues?query_id=96
>
> Do you think it is time to cut the release and ask QE to start testing ?
>
> 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
--
Mykola Golub
next prev parent reply other threads:[~2016-08-19 13:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 5:27 releasing jewel v10.2.3 ? Loic Dachary
2016-08-19 7:18 ` wido
2016-08-19 10:37 ` Alexandre DERUMIER
2016-08-19 11:00 ` Loic Dachary
2016-08-19 11:09 ` Alexandre DERUMIER
2016-08-21 14:43 ` Alexandre DERUMIER
2016-08-21 20:27 ` Loic Dachary
2016-08-22 4:35 ` Kefu Chai
2016-08-19 11:49 ` Radoslaw Zarzynski
2016-08-19 12:34 ` Loic Dachary
2016-08-19 13:05 ` Mykola Golub [this message]
2016-08-19 13:25 ` Loic Dachary
2016-08-19 14:01 ` Mykola Golub
2016-08-19 14:43 ` Loic Dachary
2016-08-19 20:16 ` Mykola Golub
2016-08-19 20:32 ` Loic Dachary
2016-08-19 13:57 ` Sage Weil
2016-08-19 14:44 ` Loic Dachary
2016-08-22 9:59 ` Fabian Grünbichler
2016-08-22 10:18 ` 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=20160819130529.GC17630@gmail.com \
--to=mgolub@mirantis.com \
--cc=abhishek.varshney@flipkart.com \
--cc=ceph-devel@vger.kernel.org \
--cc=loic@dachary.org \
--cc=sweil@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.