CEPH filesystem development
 help / color / mirror / Atom feed
From: Abhishek L <abhishek@suse.com>
To: Matt Benjamin <mbenjamin@redhat.com>,
	Orit Wasserman <owasserm@redhat.com>
Cc: Abhishek L <abhishek@suse.com>, Loic Dachary <loic@dachary.org>,
	Abhishek L <abhishek.lekshmanan@gmail.com>,
	Ceph Development <ceph-devel@vger.kernel.org>,
	Abhishek Varshney <abhishek.varshney@flipkart.com>
Subject: Re: jewel 10.2.4 freeze
Date: Tue, 25 Oct 2016 11:31:06 +0200	[thread overview]
Message-ID: <87y41cixlx.fsf@suse.com> (raw)
In-Reply-To: <618111920.22040164.1477360917772.JavaMail.zimbra@redhat.com>


Matt Benjamin writes:

> This would really be a wise idea.
>
> Matt
>
> ----- Original Message -----
>> From: "Orit Wasserman" <owasserm@redhat.com>
>> To: "Abhishek L" <abhishek@suse.com>
>> Cc: "Loic Dachary" <loic@dachary.org>, "Abhishek L" <abhishek.lekshmanan@gmail.com>, "Ceph Development"
>> <ceph-devel@vger.kernel.org>, "Abhishek Varshney" <abhishek.varshney@flipkart.com>
>> Sent: Monday, October 24, 2016 4:21:40 PM
>> Subject: Re: jewel 10.2.4 freeze
>>
>> Hi,
>> Will it be possible to include https://github.com/ceph/ceph/pull/11626 ?
>>
>> Orit

There are a few valgrind failures for RGW on the teuthology run scheduled,
http://pulpito.ceph.com/owasserm-2016-10-24_20:21:59-rgw-wip-jewel-11567---basic-vps/

(and maybe related to the patch?)
>>
>> On Mon, Oct 24, 2016 at 4:46 PM, Abhishek L <abhishek@suse.com> wrote:
>> >
>> > Loic Dachary writes:
>> >
>> >> Hi Abhishek,
>> >>
>> >> If we were to freeze jewel 10.2.4 today it would have 115 backports[0]. Do
>> >> you think it we should stop merging new backports and prepare for the
>> >> release ? If so, I'll ask the lead of each component to make sure nothing
>> >> is missing from their point of view.
>> >
>> > Yes, lets start getting the ack from the leads
>> >>
>> >> You can find the progress of the jewel 10.2.4 release in the
>> >> ttp://tracker.ceph.com/issues/17487.
>> >>
>> >> Cheers
>> >>
>> >> [0] issues backported and merged in jewel 10.2.4
>> >> http://tracker.ceph.com/versions/524
>> >>
>> >> --
>> >> Loïc Dachary, Artisan Logiciel Libre
>> >
>> >
>> > Best,
>> > Abhishek
>> > --
>> > 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
>> --
>> 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
>>


--
Abhishek Lekshmanan
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

  reply	other threads:[~2016-10-25  9:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-24 14:36 jewel 10.2.4 freeze Loic Dachary
2016-10-24 14:42 ` Loic Dachary
2016-10-24 14:46 ` Abhishek L
2016-10-24 20:21   ` Orit Wasserman
2016-10-25  2:01     ` Matt Benjamin
2016-10-25  9:31       ` Abhishek L [this message]
2016-10-25 10:34     ` Loic Dachary
2016-10-25  3:27   ` Jason Dillaman
2016-10-25 10:36     ` Loic Dachary
2016-10-25 12:40       ` kefu chai
2016-10-25 14:00         ` 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=87y41cixlx.fsf@suse.com \
    --to=abhishek@suse.com \
    --cc=abhishek.lekshmanan@gmail.com \
    --cc=abhishek.varshney@flipkart.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=loic@dachary.org \
    --cc=mbenjamin@redhat.com \
    --cc=owasserm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox