[llvm-dev] [RFC] Helping release management

[Quentin Colombet via llvm-dev]

> On May 5, 2016, at 10:08 AM, Reid Kleckner <rnk at google.com> wrote:
> 
> On Wed, May 4, 2016 at 5:07 PM, Quentin Colombet via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
> Typically, what I had in mind was things like typos/thinko, that are bugs, that we notice a few minutes after we made the “main” commit. I do not want we have to file a PR that is going to repeat what we are going to say in the commit message.
> 
> Yeah, I agree, we shouldn't have to file PRs for that kind of stuff. Quick fixes for the build or tests on other platforms obviously fall into this category.
> 
> Do release managers have problems keeping track of these kinds of changes in practice, though? You can always cut the branch from some quiescent period on the weekend of night before the cut.

Well, I think the main problem as a release manager is to not miss the follow-up commit.

Say, we branch, then two weeks later a PR comes, it gets fixed and everything is documented into the PR.
The release managers see that and pull that fix into the release.

Then, two days, later we realize we missed a case and do a follow-up commit.
There is a high chance we won’t update the PR and that the release managers will miss it, unless someone/something pings them.

Q.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160510/f10289ae/attachment.html>