[llvm] r181328 - Mention SystemZ in the release notes

Sean Silva silvas at purdue.edu
Tue May 7 10:08:50 PDT 2013


On Tue, May 7, 2013 at 11:03 AM, Rafael EspĂ­ndola <
rafael.espindola at gmail.com> wrote:

> > It seems highly error-prone to try to merge these one by one. Maybe it
> would
> > be better to just merge the whole document right before the release is
> made?
> > That would avoid anything falling through the cracks. Or I guess it
> doesn't
> > hurt to merge as we go, and then merge the whole document to make sure
> > nothing got lost.
>
> A related problem is where to put the 3.4 release notes. IMHO we
> should merge what we have to 3.3 and start the 3.4 release notes. Any
> new additions to the 3.3 release notes should then go directly to the
> 3.3 branch.
>

Yeah, that's tricky. In our git setup, is there a way to commit these
updates directly to the release branch? (I'm guessing that it's possible
from SVN, but I'm clueless about SVN). If it's not possible to commit
directly to the 3.3 release notes from git, then that would be a severe
inconvenience for git users.

If it is possible to commit directly in some easy way, then we should
probably clean out the trunk release notes and have them be the "3.4"
release notes, with a prominent warning at the top to tell developers to
commit directly to the release branch for 3.3 updates.

-- Sean Silva
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20130507/d2b9449d/attachment.html>


More information about the llvm-commits mailing list