Some of the rados errors look concerning, I'll have a look. -Sam
On Fri, Jan 16, 2015 at 12:34 PM, Loic Dachary <l...@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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
