[Release-testers] [llvm-dev] [Openmp-dev] RFC: Upcoming release schedules and creating a formal schedule for future releases

[Blower, Melanie I via Release-testers]

Tom, how did you detect the libclang ABI regression, is there automatic testing? Was there a discussion on the email lists, I missed it, would like to learn more. --Melanie 

> -----Original Message-----
> From: llvm-dev <llvm-dev-bounces at lists.llvm.org> On Behalf Of Hans
> Wennborg via llvm-dev
> Sent: Wednesday, January 6, 2021 3:20 AM
> To: Tom Stellard <tstellar at redhat.com>
> Cc: llvm-dev <llvm-dev at lists.llvm.org>; Release-testers <release-
> testers at lists.llvm.org>; clang developer list <cfe-dev at lists.llvm.org>; openmp-
> dev (openmp-dev at lists.llvm.org) <openmp-dev at lists.llvm.org>; LLDB Dev
> <lldb-dev at lists.llvm.org>
> Subject: Re: [llvm-dev] [Openmp-dev] RFC: Upcoming release schedules and
> creating a formal schedule for future releases
> 
> This sounds good to me (maybe spell out roughly what date 2.0.0-rc1 would be
> to make it easier to get an overview).
> 
> Thanks,
> Hans
> 
> On Tue, Jan 5, 2021 at 5:33 AM Tom Stellard via Openmp-dev <openmp-
> dev at lists.llvm.org> wrote:
> >
> > Hi,
> >
> > I want to give an update on the status of the LLVM 11 and LLVM 12
> > releases.  11.0.1-final is expected to be tagged this week, along with
> > 11.1.0-rc1.  Unfortunately, we had an ABI regression in libclang.so
> > between LLVM 10 and LLVM 11, so we need to do an 11.1.0 release to
> > correct this.  This happened one other time where we had to bump the
> > minor version to correct an ABI breakage.  So, LLVM 11.0.1 libclang
> > will be ABI compatible with LLVM 11, and LLVM 11.1.0 libclang will be
> > ABI compatible  with LLVM != 11.
> >
> > For LLVM 12 the proposed branch date is Jan 26.  I'm hoping we will
> > have the 2 LLVM 11.x releases done before that.
> >
> > In addition to all this, I would like to propose an official
> > week-of-the-year based release schedule that we can use for all future
> > releases.  What I'm proposing is not really any different in terms of
> > dates from what we've been doing for the last several years.  My main
> > goal is just to get this documented so it's clear to the community and
> > the release managers what the expectations are.  Here is the proposed
> > scheduled:
> >
> > 1.0.0-rc1   4th Tue in January
> > 1.0.0-rc2   + 4 Weeks
> > 1.0.0-final + 2 Weeks  (10th Tuesday ~mar 9)
> > 1.0.1-rc1   + 4 Weeks
> > 1.0.1-rc2   + 4 Weeks
> > 1.0.1-final + 2 Weeks  (20th Tuesday ~may 18)
> >
> > 2.0.0-rc1   + 10 Weeks (+26 Weeks From 1.0.0-rc1)
> > 2.0.0-rc2   +  4 Weeks
> > 2.0.0-final +  2 weeks (36th Tuesday ~sep 7)
> > 2.0.1-rc1   +  4 weeks
> > 2.0.1-rc2   +  4 weeks
> > 2.0.1-final +  2 weeks (46th Tuesday ~nov 16
> >
> > The release branches will be created on the same day as -rc1.
> >
> > If there are no objections to this, I will add it to the documentation
> > next week.
> >
> > -Tom
> >
> > _______________________________________________
> > Openmp-dev mailing list
> > Openmp-dev at lists.llvm.org
> > https://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev