On Fri, Apr 20, 2018 at 8:43 AM, Abhishek Lekshmanan <abhishek@xxxxxxxx> wrote: > > After Luminous' branch freeze at > 64ffa817000d59d91379f7335439845930f58530 there have been ~58 commits in > the branch now. Since some of the commits are in core we might need to > redo at least some of the QE validation which was relatively green > earlier. what is preventing from using '-next' branch or similar to use for release testing and make the final release? Right now we don't have any strict policies in place that can > prevent merges, at the very least an approval from the component lead > and an assessment of the suites required to rerun etc. will help us > really evaluating whether the changeset really needs to go in this > release cycle and what impact it can have on the QE > > We still haven't opened Luminous branch for merges yet, so please > contact Yuri and the backports team/post in the mailing list before > merging. > -- > Abhishek Lekshmanan > SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, > HRB 21284 (AG Nürnberg) > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > 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@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
