upcoming release giant v0.87.1 : leads feedback needed

upcoming release giant v0.87.1 : leads feedback needed

[Loic Dachary]

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

Hi Ceph,

The https://github.com/ceph/ceph/tree/giant-backports branch was tested with the rgw, rados and rbd suites. The results of each suite have been analyzed and summarized in http://tracker.ceph.com/issues/10501. The next steps are either:

a) Yehuda for rgw, Josh for rbd and Sam for rados all agree that the errors are unrelated to the backports
b) The https://github.com/ceph/ceph/tree/giant-backports branch is given to QE for final tests and merge into giant

OR

a) At least of the lead thinks more work is needed to stabilize the giant branch
b) A new set of tests will be run and analyzed after adding/removing one or more backports to/from the https://github.com/ceph/ceph/tree/giant-backports branch

The description of http://tracker.ceph.com/issues/10501 shows a detailed list of all commits / issues that are in the giant backport branch. To get a global view of what the next giant point release will be, the description also includes the commits that have already been merged in the giant branch. The list of pull requests that are candidate for inclusion in the giant release but have not been included in the integration branch are also listed: maybe one of them could contribute to resolve a problem found during the tests. And finally all redmine issues that have been marked to be backported to giant but do not yet have a candidate pull request are listed: this is the backport backlog so to speak ;-)

Cheers

-- 
Loïc Dachary, Artisan Logiciel Libre




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

Re: upcoming release giant v0.87.1 : leads feedback needed

[Loic Dachary]

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

Hi Again,

Well, this is a little embarassing but here it is : there won't be a point release for giant. I'll update the redmine tickets to remove the "giant" backport targets as well as the github milestone list accordingly.

Sorry for the noise.

On 15/01/2015 17:12, Loic Dachary wrote:
> Hi Ceph,
> 
> The https://github.com/ceph/ceph/tree/giant-backports branch was tested with the rgw, rados and rbd suites. The results of each suite have been analyzed and summarized in http://tracker.ceph.com/issues/10501. The next steps are either:
> 
> a) Yehuda for rgw, Josh for rbd and Sam for rados all agree that the errors are unrelated to the backports
> b) The https://github.com/ceph/ceph/tree/giant-backports branch is given to QE for final tests and merge into giant
> 
> OR
> 
> a) At least of the lead thinks more work is needed to stabilize the giant branch
> b) A new set of tests will be run and analyzed after adding/removing one or more backports to/from the https://github.com/ceph/ceph/tree/giant-backports branch
> 
> The description of http://tracker.ceph.com/issues/10501 shows a detailed list of all commits / issues that are in the giant backport branch. To get a global view of what the next giant point release will be, the description also includes the commits that have already been merged in the giant branch. The list of pull requests that are candidate for inclusion in the giant release but have not been included in the integration branch are also listed: maybe one of them could contribute to resolve a problem found during the tests. And finally all redmine issues that have been marked to be backported to giant but do not yet have a candidate pull request are listed: this is the backport backlog so to speak ;-)
> 
> Cheers
> 

-- 
Loïc Dachary, Artisan Logiciel Libre


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

Re: upcoming release giant v0.87.1 : leads feedback needed

[Alexandre DERUMIER]

Hi Loic,

>>Well, this is a little embarassing but here it is : there won't be a point release for giant. I'll update the redmine tickets to remove the "giant" backport targets as well as the github milestone list accordingly. 

Is the planned to update only "longterm" support releases ? (dumpling,firefly,hammer,...) ?



----- Mail original -----
De: "Loic Dachary" <loic@dachary.org>
À: "ceph-devel" <ceph-devel@vger.kernel.org>
Envoyé: Jeudi 15 Janvier 2015 18:03:27
Objet: Re: upcoming release giant v0.87.1 : leads feedback needed

Hi Again, 

Well, this is a little embarassing but here it is : there won't be a point release for giant. I'll update the redmine tickets to remove the "giant" backport targets as well as the github milestone list accordingly. 

Sorry for the noise. 

On 15/01/2015 17:12, Loic Dachary wrote: 
> Hi Ceph, 
> 
> The https://github.com/ceph/ceph/tree/giant-backports branch was tested with the rgw, rados and rbd suites. The results of each suite have been analyzed and summarized in http://tracker.ceph.com/issues/10501. The next steps are either: 
> 
> a) Yehuda for rgw, Josh for rbd and Sam for rados all agree that the errors are unrelated to the backports 
> b) The https://github.com/ceph/ceph/tree/giant-backports branch is given to QE for final tests and merge into giant 
> 
> OR 
> 
> a) At least of the lead thinks more work is needed to stabilize the giant branch 
> b) A new set of tests will be run and analyzed after adding/removing one or more backports to/from the https://github.com/ceph/ceph/tree/giant-backports branch 
> 
> The description of http://tracker.ceph.com/issues/10501 shows a detailed list of all commits / issues that are in the giant backport branch. To get a global view of what the next giant point release will be, the description also includes the commits that have already been merged in the giant branch. The list of pull requests that are candidate for inclusion in the giant release but have not been included in the integration branch are also listed: maybe one of them could contribute to resolve a problem found during the tests. And finally all redmine issues that have been marked to be backported to giant but do not yet have a candidate pull request are listed: this is the backport backlog so to speak ;-) 
> 
> 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

Re: upcoming release giant v0.87.1 : leads feedback needed

[Loic Dachary]

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

Hi Again,

As it turns out we're going to have giant point releases after all. In a nutshell there is going to be one or two point release for giant, until Hammer is out. The backporting activity for giant will be lower than for firefly or hammer, because the idea is to focus on backporting every other release (i.e. dumpling, firefly, hammer, etc. ). 

My initial request is therefore resumed and the ticket open again.

Thanks for your patience and sorry for the confusion :-)

On 15/01/2015 18:03, Loic Dachary wrote:
> Hi Again,
> 
> Well, this is a little embarassing but here it is : there won't be a point release for giant. I'll update the redmine tickets to remove the "giant" backport targets as well as the github milestone list accordingly.
> 
> Sorry for the noise.
> 
> On 15/01/2015 17:12, Loic Dachary wrote:
>> Hi Ceph,
>>
>> The https://github.com/ceph/ceph/tree/giant-backports branch was tested with the rgw, rados and rbd suites. The results of each suite have been analyzed and summarized in http://tracker.ceph.com/issues/10501. The next steps are either:
>>
>> a) Yehuda for rgw, Josh for rbd and Sam for rados all agree that the errors are unrelated to the backports
>> b) The https://github.com/ceph/ceph/tree/giant-backports branch is given to QE for final tests and merge into giant
>>
>> OR
>>
>> a) At least of the lead thinks more work is needed to stabilize the giant branch
>> b) A new set of tests will be run and analyzed after adding/removing one or more backports to/from the https://github.com/ceph/ceph/tree/giant-backports branch
>>
>> The description of http://tracker.ceph.com/issues/10501 shows a detailed list of all commits / issues that are in the giant backport branch. To get a global view of what the next giant point release will be, the description also includes the commits that have already been merged in the giant branch. The list of pull requests that are candidate for inclusion in the giant release but have not been included in the integration branch are also listed: maybe one of them could contribute to resolve a problem found during the tests. And finally all redmine issues that have been marked to be backported to giant but do not yet have a candidate pull request are listed: this is the backport backlog so to speak ;-)
>>
>> Cheers
>>
> 

-- 
Loïc Dachary, Artisan Logiciel Libre


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

Re: upcoming release giant v0.87.1 : leads feedback needed

[Samuel Just]

Some of the rados errors look concerning, I'll have a look.
-Sam

On Fri, Jan 16, 2015 at 12:34 PM, Loic Dachary <loic@dachary.org> wrote:
> Hi Again,
>
> As it turns out we're going to have giant point releases after all. In a nutshell there is going to be one or two point release for giant, until Hammer is out. The backporting activity for giant will be lower than for firefly or hammer, because the idea is to focus on backporting every other release (i.e. dumpling, firefly, hammer, etc. ).
>
> My initial request is therefore resumed and the ticket open again.
>
> Thanks for your patience and sorry for the confusion :-)
>
> On 15/01/2015 18:03, Loic Dachary wrote:
>> Hi Again,
>>
>> Well, this is a little embarassing but here it is : there won't be a point release for giant. I'll update the redmine tickets to remove the "giant" backport targets as well as the github milestone list accordingly.
>>
>> Sorry for the noise.
>>
>> On 15/01/2015 17:12, Loic Dachary wrote:
>>> Hi Ceph,
>>>
>>> The https://github.com/ceph/ceph/tree/giant-backports branch was tested with the rgw, rados and rbd suites. The results of each suite have been analyzed and summarized in http://tracker.ceph.com/issues/10501. The next steps are either:
>>>
>>> a) Yehuda for rgw, Josh for rbd and Sam for rados all agree that the errors are unrelated to the backports
>>> b) The https://github.com/ceph/ceph/tree/giant-backports branch is given to QE for final tests and merge into giant
>>>
>>> OR
>>>
>>> a) At least of the lead thinks more work is needed to stabilize the giant branch
>>> b) A new set of tests will be run and analyzed after adding/removing one or more backports to/from the https://github.com/ceph/ceph/tree/giant-backports branch
>>>
>>> The description of http://tracker.ceph.com/issues/10501 shows a detailed list of all commits / issues that are in the giant backport branch. To get a global view of what the next giant point release will be, the description also includes the commits that have already been merged in the giant branch. The list of pull requests that are candidate for inclusion in the giant release but have not been included in the integration branch are also listed: maybe one of them could contribute to resolve a problem found during the tests. And finally all redmine issues that have been marked to be backported to giant but do not yet have a candidate pull request are listed: this is the backport backlog so to speak ;-)
>>>
>>> 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

Re: upcoming release giant v0.87.1 : leads feedback needed

[Samuel Just]

Nvm, the rados failures look normal.  That set of test results seems
fine to me from a rados point of view.
-Sam

On Fri, Jan 16, 2015 at 1:34 PM, Samuel Just <sam.just@inktank.com> wrote:
> Some of the rados errors look concerning, I'll have a look.
> -Sam
>
> On Fri, Jan 16, 2015 at 12:34 PM, Loic Dachary <loic@dachary.org> wrote:
>> Hi Again,
>>
>> As it turns out we're going to have giant point releases after all. In a nutshell there is going to be one or two point release for giant, until Hammer is out. The backporting activity for giant will be lower than for firefly or hammer, because the idea is to focus on backporting every other release (i.e. dumpling, firefly, hammer, etc. ).
>>
>> My initial request is therefore resumed and the ticket open again.
>>
>> Thanks for your patience and sorry for the confusion :-)
>>
>> On 15/01/2015 18:03, Loic Dachary wrote:
>>> Hi Again,
>>>
>>> Well, this is a little embarassing but here it is : there won't be a point release for giant. I'll update the redmine tickets to remove the "giant" backport targets as well as the github milestone list accordingly.
>>>
>>> Sorry for the noise.
>>>
>>> On 15/01/2015 17:12, Loic Dachary wrote:
>>>> Hi Ceph,
>>>>
>>>> The https://github.com/ceph/ceph/tree/giant-backports branch was tested with the rgw, rados and rbd suites. The results of each suite have been analyzed and summarized in http://tracker.ceph.com/issues/10501. The next steps are either:
>>>>
>>>> a) Yehuda for rgw, Josh for rbd and Sam for rados all agree that the errors are unrelated to the backports
>>>> b) The https://github.com/ceph/ceph/tree/giant-backports branch is given to QE for final tests and merge into giant
>>>>
>>>> OR
>>>>
>>>> a) At least of the lead thinks more work is needed to stabilize the giant branch
>>>> b) A new set of tests will be run and analyzed after adding/removing one or more backports to/from the https://github.com/ceph/ceph/tree/giant-backports branch
>>>>
>>>> The description of http://tracker.ceph.com/issues/10501 shows a detailed list of all commits / issues that are in the giant backport branch. To get a global view of what the next giant point release will be, the description also includes the commits that have already been merged in the giant branch. The list of pull requests that are candidate for inclusion in the giant release but have not been included in the integration branch are also listed: maybe one of them could contribute to resolve a problem found during the tests. And finally all redmine issues that have been marked to be backported to giant but do not yet have a candidate pull request are listed: this is the backport backlog so to speak ;-)
>>>>
>>>> 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