3.9.1 Release Schedule

Hi,

Here is a proposed release schedule for 3.9.1:

Nov 21, 2016: Deadline for nominating change to merge to the 3.9 branch
Nov 29, 2016: -rc1
Dec 5, 2015: 3.9.1 Release

As a reminder, if you would like to request a patch be merged to the 3.9
branch, file a bug at www.llvm.org/bugs with the subject "Merge rxxxxx
into the 3.9 branch." and add 30261 – [Meta] 3.9.1 Merges and Bug Fixes
as a blocking bug.

Thanks,
Tom

Hi,

Here is a proposed release schedule for 3.9.1:

Nov 21, 2016: Deadline for nominating change to merge to the 3.9 branch
Nov 29, 2016: -rc1
Dec 5, 2015: 3.9.1 Release

As a reminder, if you would like to request a patch be merged to the 3.9
branch, file a bug at www.llvm.org/bugs with the subject "Merge rxxxxx
into the 3.9 branch." and add https://llvm.org/bugs/show_bug.cgi?id=30261
as a blocking bug.

Thanks,
Tom

Tom,
     Should we also add you, as release manager, to the CC list on
these bug reports?
            Jack

> Hi,
>
> Here is a proposed release schedule for 3.9.1:
>
> Nov 21, 2016: Deadline for nominating change to merge to the 3.9 branch
> Nov 29, 2016: -rc1
> Dec 5, 2015: 3.9.1 Release
>
> As a reminder, if you would like to request a patch be merged to the 3.9
> branch, file a bug at www.llvm.org/bugs with the subject "Merge rxxxxx
> into the 3.9 branch." and add 30261 – [Meta] 3.9.1 Merges and Bug Fixes
> as a blocking bug.
>
> Thanks,
> Tom

Tom,
     Should we also add you, as release manager, to the CC list on
these bug reports?

Hi Jack,

Thanks for reminding me, you should actually assign the bugs to me.

-Tom

One of the concerns I have as an out-of-tree compiler maintainer, is with the patch releases for LLVM; and in particular not having a clear understanding of what the patch releases will fix in order to determine if they are important to me or not. For example, while X86 and ARM target fixes may be very important for a considerable number of LLVM users, in general they are not so critical to my non-X86 non-ARM target.

However, fixes to the handling of the ISO C math function builtins is.

Tracking a release out-of-tree is a huge amount of work, and I need to be careful with minimal resources not to track just for the sake of it. Is there a statement or rolling-list of proposed changes for each LLVM/CFE patch release that I can use to guide me?

Thanks,

  MartinO

Sounds good to me. Shall we update the "Upcoming Releases" on llvm.org?

Cheers,
Hans

I’ll be away for this release, I’ll try to build the final binaries when I get back.