Willem Jan Withagen <wjw@xxxxxxxxxxx> writes: > On 19-4-2018 14:45, Nathan Cutler wrote: >>> So I could have a "dormant" jenkins-builder waiting for changes to the >>> branch "Luminous", that will only trigger when backports are merged? >>> Which will then trigger when again preparation for a new release starts. >> >> It would be the branch "luminous" (lower-case). >> >>> it cost some diskspace, but other than that things will be pretty silent. >> >> There are periods of light luminous merging activity (like now), and >> heavy (10 PRs a day or even more, in the more intense stretches of the >> release preparation phase). > > Right, that would not be a problem. > I've scheduled to run Jenkins every 4 hours. > So if there are more PRs merged, it'll take them all at once. Right now luminous is in a "freeze" mode, so there shouldn't be PRs merged for some time. I'm thinking that we might need to change our backports workflow to go for luminous-next instead of luminous by default and merging to Luminous only at QE handover so that the branch is almost close to release branch and we have less issues with merges and workflow when final QE is happening. > > --WjW > > > -- 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
