Hans Wennborg via llvm-dev
2017-Jan-12 23:34 UTC
[llvm-dev] [4.0.0 Release] The branch is here, the release process starts
Dear everyone, It has begun: the release branch was recently created from trunk at r291814 and the trunk version was subsequently incremented to 5.0.0 (as per the new versioning scheme [1]). Release blockers are tracked by http://llvm.org/PR31622 Please mark any bugs, old or new, that you think need to be fixed before the release as blocking that. Please help me out in staying on top of the release by cc'ing me on any bugs, commits, or other issues you think may be relevant. If I'm not cc'd on it, there's a large chance I'll miss it. I'm on IRC too, but email is more reliable. If you know of any committs that occurred close to the branch that need to be reverted or merged, please let me know. To get a change committed to the branch, first commit to trunk as usual, and then reply to the commit message on the mailing list with myself and the code owner cc'd, asking for the change to be merged to the branch. Alternatively, make the request by filing a bug blocking PR31622. Release notes should be committed directly to the branch. If you know of any significant change made since the last release, it should get mentioned in the notes. What's next? Once the branch is in good shape, hopefully within a few days, a first release candidate will be made available for testing. The schedule for the release is under "Upcoming Releases" on http://llvm.org. Thanks, Hans [1] http://blog.llvm.org/2016/12/llvms-new-versioning-scheme.html
Nicolai Hähnle via llvm-dev
2017-Jan-13 13:49 UTC
[llvm-dev] [4.0.0 Release] The branch is here, the release process starts
I don't see the release branch in the Git mirror at http://llvm.org/git/llvm.git yet. Is that going to appear soon? Thanks, Nicolai On 13.01.2017 00:34, Hans Wennborg via llvm-dev wrote:> Dear everyone, > > It has begun: the release branch was recently created from trunk at > r291814 and the trunk version was subsequently incremented to 5.0.0 > (as per the new versioning scheme [1]). > > Release blockers are tracked by http://llvm.org/PR31622 Please mark > any bugs, old or new, that you think need to be fixed before the > release as blocking that. > > Please help me out in staying on top of the release by cc'ing me on > any bugs, commits, or other issues you think may be relevant. If I'm > not cc'd on it, there's a large chance I'll miss it. I'm on IRC too, > but email is more reliable. > > If you know of any committs that occurred close to the branch that > need to be reverted or merged, please let me know. > > To get a change committed to the branch, first commit to trunk as > usual, and then reply to the commit message on the mailing list with > myself and the code owner cc'd, asking for the change to be merged to > the branch. Alternatively, make the request by filing a bug blocking > PR31622. > > Release notes should be committed directly to the branch. If you know > of any significant change made since the last release, it should get > mentioned in the notes. > > What's next? Once the branch is in good shape, hopefully within a few > days, a first release candidate will be made available for testing. > The schedule for the release is under "Upcoming Releases" on > http://llvm.org. > > Thanks, > Hans > > > [1] http://blog.llvm.org/2016/12/llvms-new-versioning-scheme.html > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >
Hans Wennborg via llvm-dev
2017-Jan-13 17:23 UTC
[llvm-dev] [4.0.0 Release] The branch is here, the release process starts
It's there for me now: $ git fetch origin remote: Counting objects: 811, done. remote: Compressing objects: 100% (561/561), done. remote: Total 562 (delta 462), reused 2 (delta 0) Receiving objects: 100% (562/562), 927.00 KiB | 1.29 MiB/s, done. Resolving deltas: 100% (462/462), completed with 240 local objects.>From http://llvm.org/git/llvm233ecbde652..16c5e12d3a5 master -> origin/master * [new branch] release_40 -> origin/release_40 On Fri, Jan 13, 2017 at 5:49 AM, Nicolai Hähnle <nhaehnle at gmail.com> wrote:> I don't see the release branch in the Git mirror at > http://llvm.org/git/llvm.git yet. Is that going to appear soon? > > Thanks, > Nicolai > > > On 13.01.2017 00:34, Hans Wennborg via llvm-dev wrote: >> >> Dear everyone, >> >> It has begun: the release branch was recently created from trunk at >> r291814 and the trunk version was subsequently incremented to 5.0.0 >> (as per the new versioning scheme [1]). >> >> Release blockers are tracked by http://llvm.org/PR31622 Please mark >> any bugs, old or new, that you think need to be fixed before the >> release as blocking that. >> >> Please help me out in staying on top of the release by cc'ing me on >> any bugs, commits, or other issues you think may be relevant. If I'm >> not cc'd on it, there's a large chance I'll miss it. I'm on IRC too, >> but email is more reliable. >> >> If you know of any committs that occurred close to the branch that >> need to be reverted or merged, please let me know. >> >> To get a change committed to the branch, first commit to trunk as >> usual, and then reply to the commit message on the mailing list with >> myself and the code owner cc'd, asking for the change to be merged to >> the branch. Alternatively, make the request by filing a bug blocking >> PR31622. >> >> Release notes should be committed directly to the branch. If you know >> of any significant change made since the last release, it should get >> mentioned in the notes. >> >> What's next? Once the branch is in good shape, hopefully within a few >> days, a first release candidate will be made available for testing. >> The schedule for the release is under "Upcoming Releases" on >> http://llvm.org. >> >> Thanks, >> Hans >> >> >> [1] http://blog.llvm.org/2016/12/llvms-new-versioning-scheme.html >> _______________________________________________ >> LLVM Developers mailing list >> llvm-dev at lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >> >
Maybe Matching Threads
- [4.0.0 Release] The branch is here, the release process starts
- [4.0.0 Release] The branch is here, the release process starts
- [cfe-dev] [4.0.0 Release] Relase Candidate 1 has been tagged
- [cfe-dev] [4.0.0 Release] Release Candidate 2 source and binaries available
- Possible stack corruption during call to JITSymbol::getAddress()