Seems lld's release_50 has been created. Openmp's release_50 isn't there. Committing branches doesn't trigger git-svn. Release_50 will be created when someone committed something in trunk.
On Fri, Jul 21, 2017 at 1:05 AM Khem Raj via llvm-dev < llvm-...@lists.llvm.org> wrote: > Hi Hans > > On Wed, Jul 19, 2017 at 11:54 AM, Hans Wennborg via llvm-dev > <llvm-...@lists.llvm.org> wrote: > > Dear everyone, > > > > The release branch was recently created from trunk at r308441 and the > > trunk version was subsequently incremented to 6.0.0. > > > > Release blockers are tracked by > > https://bugs.llvm.org/show_bug.cgi?id=33849 Please mark any bugs, old > > or new, that you think need to be fixed before the release as blocking > > that. > > > > Please help out with the release by notifying me of any bugs, commits, > > or other issues you think might be relevant; ideally by marking them > > as blockers of the bug above. If it's not on that bug, or I'm not cc'd > > on an email about it, I'll probably miss it. > > > > To get a change committed to the branch, first commit it to trunk as > > usual, and then request it to be merged -- ideally by filing a blocker > > bug on PR33849, or by cc'ing me on the commit email. > > > > What's next? Once the branch is in good shape, a first release > > candidate will be made available for testing. The schedule for the > > release is under "Upcoming Releases" on http://llvm.org. > > > > It seems lldb is not branched yet. Do you know when that will happen ? > _______________________________________________ > LLVM Developers mailing list > llvm-...@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >
_______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
