From: Abhishek Lekshmanan <abhishek@suse.com>
To: kefu chai <tchaikov@gmail.com>
Cc: Sage Weil <sweil@redhat.com>,
Yehuda Sadeh-Weinraub <yehuda@redhat.com>,
Matt Benjamin <mbenjami@redhat.com>,
"Durgin, Josh" <jdurgin@redhat.com>,
Patrick Donnelly <pdonnell@redhat.com>,
Jason Dillaman <jdillama@redhat.com>,
John Spray <jspray@redhat.com>,
Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Are we ready for Luminous?
Date: Wed, 23 Aug 2017 16:00:56 +0200 [thread overview]
Message-ID: <87pobmqt7r.fsf@suse.com> (raw)
In-Reply-To: <CAJE9aOMhuzp-VNX4t7DByqUz78HOLvxgR-p8waX_EdRsgtqBKw@mail.gmail.com>
kefu chai <tchaikov@gmail.com> writes:
> On Wed, Aug 23, 2017 at 7:26 PM, Abhishek Lekshmanan <abhishek@suse.com> wrote:
>>
>> Other than the existing PRs in https://github.com/ceph/ceph/milestone/10,
>> do we have anything else that really needs to go in for Luminous? Any
>> other blockers?
>
> and all tracker tickets whose "backport" has "luminous", and pending
> on packport [0]. and all needs-backport PRs which are not yet
> backported [1].
>
> ---
> [0] http://tracker.ceph.com/projects/rados/issues?utf8=✓&set_filter=1&f%5B%5D=status_id&op%5Bstatus_id%5D=%21&v%5Bstatus_id%5D%5B%5D=3&f%5B%5D=cf_2&op%5Bcf_2%5D=%7E&v%5Bcf_2%5D%5B%5D=luminous&f%5B%5D=&c%5B%5D=project&c%5B%5D=tracker&c%5B%5D=status&c%5B%5D=priority&c%5B%5D=subject&c%5B%5D=assigned_to&c%5B%5D=updated_on&c%5B%5D=category&c%5B%5D=fixed_version&c%5B%5D=cf_3&group_by=&t%5B%5D=
Staged a backport for the ones which are already in the Pending Backport
stage (The ones in pending review state are still awaiting comments etc
in a few)
> [1] https://github.com/ceph/ceph/pulls?utf8=✓&q=is%3Apr%20label%3Aneeds-backport%20.
> quite a few of PRs in this list have been backported.
Just started creating issues for these so that they are easier to track
--
Abhishek
next prev parent reply other threads:[~2017-08-23 14:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 11:26 Are we ready for Luminous? Abhishek Lekshmanan
2017-08-23 13:11 ` kefu chai
2017-08-23 14:00 ` Abhishek Lekshmanan [this message]
2017-08-23 13:46 ` John Spray
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=87pobmqt7r.fsf@suse.com \
--to=abhishek@suse.com \
--cc=ceph-devel@vger.kernel.org \
--cc=jdillama@redhat.com \
--cc=jdurgin@redhat.com \
--cc=jspray@redhat.com \
--cc=mbenjami@redhat.com \
--cc=pdonnell@redhat.com \
--cc=sweil@redhat.com \
--cc=tchaikov@gmail.com \
--cc=yehuda@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.