llvm dev - Jul 2020 - [11.0.0 Release] The release branch is here; trunk is now 12.0.0

Hello everyone,

The release branch for LLVM 11 was created from the trunk at
2e10b7a39b930ef8d9c4362509d8835b221fbc0a, and the trunk version was
bumped to 12.0.0.

Release blockers are tracked by https://llvm.org/PR46725 Please mark
any bugs, old or new, that need to be fixed before the release as
blocking that bug.

Please keep me in the loop via email on any bugs, commits, or other
issues that might be relevant for the release. In particular, if
you're currently investigating issues with trunk and working on fixes,
please help me make sure that those fixes end up on the branch also.

To get a change committed to the branch, please commit it to trunk as
per usual, and then request it to be merged -- ideally by filing a
blocker of https://llvm.org/PR46725, or by cc'ing me on the commit
email.

(Please don't report issues or request merges over
IRC/Discord/Discourse; there's a large risk that I'll miss it. Please
use email.)

The first release candidate will be tagged soon (hopefully in a day or
two if the branch looks stable), and testing of that can begin. The
full release schedule can be found under "Upcoming Releases" to the
right at https://llvm.org

Thanks,
Hans

Hi Hans,
> The release branch for LLVM 11 was created from the trunk at
> 2e10b7a39b930ef8d9c4362509d8835b221fbc0a, and the trunk version was
> bumped to 12.0.0.
[...]
> The first release candidate will be tagged soon (hopefully in a day or
> two if the branch looks stable), and testing of that can begin. The
> full release schedule can be found under "Upcoming Releases" to
the
> right at https://llvm.org
I noticed that the test-release.sh script currently lacks support to
include flang in the build.  Is this intentional or just an oversight?

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

On Wed, Jul 15, 2020 at 2:20 PM Rainer Orth <ro at gcc.gnu.org>
wrote:
>
> Hi Hans,
>
> > The release branch for LLVM 11 was created from the trunk at
> > 2e10b7a39b930ef8d9c4362509d8835b221fbc0a, and the trunk version was
> > bumped to 12.0.0.
> [...]
> > The first release candidate will be tagged soon (hopefully in a day or
> > two if the branch looks stable), and testing of that can begin. The
> > full release schedule can be found under "Upcoming Releases"
to the
> > right at https://llvm.org
>
> I noticed that the test-release.sh script currently lacks support to
> include flang in the build.  Is this intentional or just an oversight?
It hasn't been added yet since flang wasn't in the tree for the last
release.

flang-dev folks: what is the current flang status? Should it be added
to the llvm/utils/release/test-release.sh script so that it gets
testing and prebuilt binaries as part of the release?

Thanks for tagging, Hans. Can I go ahead with the CMake version bump advertised
in http://lists.llvm.org/pipermail/llvm-dev/2020-June/142893.html?

This may cause some instability on a few builders that have not upgraded to a
recent CMake yet, but I'll iterate as explained in the linked thread. Let me
know if it's OK to go ahead now or if you'd prefer that I wait for a few
days.

Cheers,
Louis
> On Jul 15, 2020, at 08:09, Hans Wennborg via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
> 
> Hello everyone,
> 
> The release branch for LLVM 11 was created from the trunk at
> 2e10b7a39b930ef8d9c4362509d8835b221fbc0a, and the trunk version was
> bumped to 12.0.0.
> 
> Release blockers are tracked by https://llvm.org/PR46725 Please mark
> any bugs, old or new, that need to be fixed before the release as
> blocking that bug.
> 
> Please keep me in the loop via email on any bugs, commits, or other
> issues that might be relevant for the release. In particular, if
> you're currently investigating issues with trunk and working on fixes,
> please help me make sure that those fixes end up on the branch also.
> 
> To get a change committed to the branch, please commit it to trunk as
> per usual, and then request it to be merged -- ideally by filing a
> blocker of https://llvm.org/PR46725, or by cc'ing me on the commit
> email.
> 
> (Please don't report issues or request merges over
> IRC/Discord/Discourse; there's a large risk that I'll miss it.
Please
> use email.)
> 
> The first release candidate will be tagged soon (hopefully in a day or
> two if the branch looks stable), and testing of that can begin. The
> full release schedule can be found under "Upcoming Releases" to
the
> right at https://llvm.org
> 
> Thanks,
> Hans
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

Hello Hans,

Also on the subject of flang, I've pushed a couple of commits today to
allow shared library builds when flang is enabled as a subproject.
Would it be possible to have these merged accross to the release branch
so we can have working shared library builds there?

The commits are
https://reviews.llvm.org/rG1c93671e594d075cb0008dc4f33d863611af9ab9
and 
https://reviews.llvm.org/rG920e127e02531640204be0944a37bd3bf449f66b

Thanks!
David Truby

On Wed, 2020-07-15 at 14:09 +0200, Hans Wennborg via llvm-dev
wrote:
> Hello everyone,
> 
> The release branch for LLVM 11 was created from the trunk at
> 2e10b7a39b930ef8d9c4362509d8835b221fbc0a, and the trunk version was
> bumped to 12.0.0.
> 
> Release blockers are tracked by https://llvm.org/PR46725 Please mark
> any bugs, old or new, that need to be fixed before the release as
> blocking that bug.
> 
> Please keep me in the loop via email on any bugs, commits, or other
> issues that might be relevant for the release. In particular, if
> you're currently investigating issues with trunk and working on
> fixes,
> please help me make sure that those fixes end up on the branch also.
> 
> To get a change committed to the branch, please commit it to trunk as
> per usual, and then request it to be merged -- ideally by filing a
> blocker of https://llvm.org/PR46725, or by cc'ing me on the commit
> email.
> 
> (Please don't report issues or request merges over
> IRC/Discord/Discourse; there's a large risk that I'll miss it.
Please
> use email.)
> 
> The first release candidate will be tagged soon (hopefully in a day
> or
> two if the branch looks stable), and testing of that can begin. The
> full release schedule can be found under "Upcoming Releases" to
the
> right at https://llvm.org
> 
> Thanks,
> Hans
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

Sounds good to me.

On Wed, Jul 15, 2020 at 8:25 PM Louis Dionne <ldionne at apple.com>
wrote:
>
> Thanks for tagging, Hans. Can I go ahead with the CMake version bump
advertised in http://lists.llvm.org/pipermail/llvm-dev/2020-June/142893.html?
>
> This may cause some instability on a few builders that have not upgraded to
a recent CMake yet, but I'll iterate as explained in the linked thread. Let
me know if it's OK to go ahead now or if you'd prefer that I wait for a
few days.
>
> Cheers,
> Louis
>
> > On Jul 15, 2020, at 08:09, Hans Wennborg via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
> >
> > Hello everyone,
> >
> > The release branch for LLVM 11 was created from the trunk at
> > 2e10b7a39b930ef8d9c4362509d8835b221fbc0a, and the trunk version was
> > bumped to 12.0.0.
> >
> > Release blockers are tracked by https://llvm.org/PR46725 Please mark
> > any bugs, old or new, that need to be fixed before the release as
> > blocking that bug.
> >
> > Please keep me in the loop via email on any bugs, commits, or other
> > issues that might be relevant for the release. In particular, if
> > you're currently investigating issues with trunk and working on
fixes,
> > please help me make sure that those fixes end up on the branch also.
> >
> > To get a change committed to the branch, please commit it to trunk as
> > per usual, and then request it to be merged -- ideally by filing a
> > blocker of https://llvm.org/PR46725, or by cc'ing me on the commit
> > email.
> >
> > (Please don't report issues or request merges over
> > IRC/Discord/Discourse; there's a large risk that I'll miss it.
Please
> > use email.)
> >
> > The first release candidate will be tagged soon (hopefully in a day or
> > two if the branch looks stable), and testing of that can begin. The
> > full release schedule can be found under "Upcoming Releases"
to the
> > right at https://llvm.org
> >
> > Thanks,
> > Hans
> > _______________________________________________
> > LLVM Developers mailing list
> > llvm-dev at lists.llvm.org
> > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>

On 7/15/20 5:09 AM, Hans Wennborg via llvm-dev wrote:
> The first release candidate will be tagged soon (hopefully in a day or
> two if the branch looks stable), and testing of that can begin. The
> full release schedule can be found under "Upcoming Releases" to
the
> right at https://llvm.org
Hi - do you have a new estimate when that release candidate is coming?
I do see blockers on the tracking bug, but I wasn't sure if that would
delay RC1 entirely.

We're eager to update this for rustc because the build performance has
improved since 10 (I'll share numbers later), but I thought it would be
prudent for us to at least wait for RC1.

Thanks,
Josh

On Mon, Jul 27, 2020 at 6:41 PM Josh Stone via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
>
> On 7/15/20 5:09 AM, Hans Wennborg via llvm-dev wrote:
> > The first release candidate will be tagged soon (hopefully in a day or
> > two if the branch looks stable), and testing of that can begin. The
> > full release schedule can be found under "Upcoming Releases"
to the
> > right at https://llvm.org
>
> Hi - do you have a new estimate when that release candidate is coming?
> I do see blockers on the tracking bug, but I wasn't sure if that would
> delay RC1 entirely.
>
> We're eager to update this for rustc because the build performance has
> improved since 10 (I'll share numbers later), but I thought it would be
> prudent for us to at least wait for RC1.
RC1 was tagged earlier today. I'm just doing the final preparations
before sending out the announcement email.

Thanks,
Hans