From: Abhishek L <abhishek@suse.com>
To: Nathan Cutler <ncutler@suse.cz>
Cc: Abhishek Lekshmanan <abhishek@suse.com>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Are we ready for jewel 10.2.6?
Date: Wed, 01 Feb 2017 16:45:16 +0100 [thread overview]
Message-ID: <87mve5vrsj.fsf@suse.com> (raw)
In-Reply-To: <63289246-25fb-c96f-b844-dba82d7293c5@suse.cz>
Nathan Cutler writes:
> Hi Abhishek:
>
> The stable releases and backports team has been working to prepare the
> Jewel 10.2.6 release and so far we have merged a large number of
> bugfixes and even some features that were judged to be worth backporting.
>
> I don't have a full list, yet, because I'm still merging RGW backports
> and there a few more miscellaneous backports still in the queue. The
> integration tests are looking better and better, and I expect these will
> be merged within the next week or two.
>
> Do you think it's time to publish a 10.2.6 point release?
Yes, lets start getting the leads approval and handover to QE
--
Abhishek Lekshmanan
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2017-02-01 15:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 15:35 Are we ready for jewel 10.2.6? Nathan Cutler
2017-02-01 15:45 ` Abhishek L [this message]
2017-02-01 17:17 ` Wido den Hollander
2017-02-01 17:23 ` Wyllys Ingersoll
2017-02-02 10:50 ` Nathan Cutler
2017-02-02 7:06 ` Piotr Dałek
2017-02-02 8:22 ` Loic Dachary
2017-02-02 9:02 ` Piotr Dałek
2017-02-02 10:52 ` Nathan Cutler
2017-02-02 13:19 ` Bartłomiej Święcki
2017-02-03 6:11 ` Alexey Sheplyakov
2017-02-03 7:02 ` Loic Dachary
2017-02-09 5:10 ` Brad Hubbard
2017-02-16 10:55 ` Dan van der Ster
2017-02-16 11:00 ` Wido den Hollander
2017-02-17 20:13 ` Vaibhav Bhembre
2017-02-20 14:57 ` Nathan Cutler
2017-02-20 18:20 ` Josh Durgin
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=87mve5vrsj.fsf@suse.com \
--to=abhishek@suse.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.