[llvm-dev] [RFC] Helping release management

Robinson, Paul via llvm-dev llvm-dev at lists.llvm.org
Thu May 5 11:47:24 PDT 2016

Filing a PR for *every* fix is overkill.  But filing a PR to express "please merge this to the branch" (if there isn't already a PR) seems reasonable.

From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Reid Kleckner via llvm-dev
Sent: Thursday, May 05, 2016 10:09 AM
To: Quentin Colombet
Cc: llvm-dev
Subject: Re: [llvm-dev] [RFC] Helping release management

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160505/c480d3be/attachment-0001.html>

More information about the llvm-dev mailing list