All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Gregory Farnum <greg@gregs42.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>,
	Abhishek L <abhishek.lekshmanan@gmail.com>
Subject: Re: CephFS and the next giant release v0.87.2
Date: Fri, 17 Apr 2015 01:16:53 +0200	[thread overview]
Message-ID: <553042E5.4040501@dachary.org> (raw)
In-Reply-To: <CAC6JEv8iAOHb2+R9TXFwQ0BnmaY-zYfq4E7MzZsK_Doa7LN5gA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1695 bytes --]

Hi Greg,

On 17/04/2015 00:44, Gregory Farnum wrote:
> On Wed, Apr 15, 2015 at 2:37 AM, Loic Dachary <loic@dachary.org> wrote:
>> Hi Greg,
>>
>> The next giant release as found at https://github.com/ceph/ceph/tree/giant passed the fs suite (http://tracker.ceph.com/issues/11153#fs). Do you think it is ready for QE to start their own round of testing ?
>>
>> Note that it will be the last giant release.
>>
>> Cheers
>>
>> P.S. http://tracker.ceph.com/issues/11153#Release-information has direct links to the pull requests merged into giant since v0.87.1 in case you need more context about one of them.
> 
> All those PRs look like fine ones to release.
> 
> I remember you went through a big purge of giant-tagged backports at
> one point though (when we thought we weren't going to do any more
> releases at all). Did that get somehow undone and all of those dealt
> with? 

I inadvertendly closed a few issue that I should not have (less than 10 more than 5 IIRC). I carefully reviewed all of them and they have been dealt with indeed. There now is a HOWTO to prevent that kind of mistake, hopefully. http://tracker.ceph.com/projects/ceph-releases/wiki/HOWTO_resolve_issues_that_are_Pending_Backport

> Some of them were more important than others and it would be
> some work for me to reconstruct the list, but I'll need to do that if
> you haven't already. :/

There are a four giant issues that are candidate for backporting : http://tracker.ceph.com/projects/ceph/issues?query_id=68, only one of which is related to CephFS. Do you think it must be included in this last giant release ?

Cheers

> -Greg
> 

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2015-04-16 23:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-15  9:37 CephFS and the next giant release v0.87.2 Loic Dachary
2015-04-16 22:44 ` Gregory Farnum
2015-04-16 23:16   ` Loic Dachary [this message]
2015-04-16 23:22     ` Gregory Farnum

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=553042E5.4040501@dachary.org \
    --to=loic@dachary.org \
    --cc=abhishek.lekshmanan@gmail.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=greg@gregs42.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.