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

[via llvm-dev]

I looked at calendars for upcoming years; the 2.0.0 date ends up being less predictable than I’d like.  Mostly it’s the 4th Tuesday in July, but sometimes the 5th Tuesday, and can be 4th Tuesday even when there is a 5th Tuesday.

Rather than 2.0.0-rc1 = 1.0.0-rc1 + 26 weeks, let’s make it 2.0.0-rc1 = 4th Tuesday in July (i.e., 1.0.0-rc1 plus 6 months, not plus 26 weeks).  I think that will be easier to remember, and the interval being a week shorter should not be a problem.
--paulr

From: lldb-dev <lldb-dev-bounces at lists.llvm.org> On Behalf Of Renato Golin via lldb-dev
Sent: Wednesday, January 6, 2021 5:39 AM
To: Hans Wennborg <hans at chromium.org>
Cc: llvm-dev <llvm-dev at lists.llvm.org>; Release-testers <release-testers 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>; clang developer list <cfe-dev at lists.llvm.org>
Subject: Re: [lldb-dev] [llvm-dev] [Openmp-dev] RFC: Upcoming release schedules and creating a formal schedule for future releases

On Wed, 6 Jan 2021 at 08:20, Hans Wennborg via llvm-dev <llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>> wrote:
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).

How about we specify the week, rather than the day?

If our aim is Tuesday, then it'll often be early in the week, so people won't be waiting too long, but allows some flexibility if something bad happens and avoids multiple emails on the list about "where's the release?".
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20210106/f6f96bf0/attachment.html>