llvm dev - Apr 2016 - [cfe-dev] 3.8.1 Release Schedule

Hi,

It's about time to start thinking about the 3.8.1 release.  Here
is a proposed release schedule:

May 25 - Deadline to request a change be merged to the 3.8 branch.
June 1 - Deadline to merge changes to the 3.8 branch.
June 1 - 3.8.1-rc1
June 8 - 3.8.1-rc2 (if necessary)
June 15 - 3.8.1 Release

If you want a patch included in the 3.8.1 release, send an email
to llvm-commits with the subject: "3.8 Merge Request: r123456".
Make sure to cc me and the code owner.  Once you get approval from
the code owner and me, then you can merge the patch to the 3.8 branch.
If you don't have commit access or are unable to commit the patch, let
me know.

For the 3.7.1 release, I encouraged people to make stable patch requests using
phabricator's audit tool.  This did not work out as well as I had hoped,
so I would prefer if people made requests via email.  However, I will
still accept merge requests via audit.

As always, we need release testers.  If you are interested, send me an
email with the platform you can test and also subscribe to the
release-testers mailing list:
http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers

Thanks,
Tom

On 22 April 2016 at 16:29, Tom Stellard via cfe-dev
<cfe-dev at lists.llvm.org> wrote:
> May 25 - Deadline to request a change be merged to the 3.8 branch.
> June 1 - Deadline to merge changes to the 3.8 branch.
> June 1 - 3.8.1-rc1
> June 8 - 3.8.1-rc2 (if necessary)
> June 15 - 3.8.1 Release
Hi Tom,

I'm assuming 3.9 will be starting early/mid July, so this may be too
close. Maybe move it up two/three weeks?

> As always, we need release testers.  If you are interested, send me an
> email with the platform you can test and also subscribe to the
> release-testers mailing list:
> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
ARM and AArch64, reporting for duty. :)

--renato

What fixes are being proposed for 3.8.1 versus 3.8?

I carefully tracked 3.7 to 3.7.1 one changes, but 3.8 came so close on its heels
that it turned out I shipped 3.8 to my customers and not the 3.7.1 patch.

Is it actually worth the effort?  If it has important fixes my vote would be
"yes", but I'd really like to know in advance what the vx.y.N
offers over the vx.y.(N-1) in terms of stability, fixes, correctness, etc., and
this information seems to be unavailable.

	MartinO

-----Original Message-----
From: cfe-dev [mailto:cfe-dev-bounces at lists.llvm.org] On Behalf Of Tom
Stellard via cfe-dev
Sent: 22 April 2016 16:30
To: llvm-dev at lists.llvm.org; cfe-dev at lists.llvm.org
Cc: release-testers at lists.llvm.org
Subject: [cfe-dev] 3.8.1 Release Schedule

Hi,

It's about time to start thinking about the 3.8.1 release.  Here is a
proposed release schedule:

May 25 - Deadline to request a change be merged to the 3.8 branch.
June 1 - Deadline to merge changes to the 3.8 branch.
June 1 - 3.8.1-rc1
June 8 - 3.8.1-rc2 (if necessary)
June 15 - 3.8.1 Release

If you want a patch included in the 3.8.1 release, send an email to llvm-commits
with the subject: "3.8 Merge Request: r123456".
Make sure to cc me and the code owner.  Once you get approval from the code
owner and me, then you can merge the patch to the 3.8 branch.
If you don't have commit access or are unable to commit the patch, let me
know.

For the 3.7.1 release, I encouraged people to make stable patch requests using
phabricator's audit tool.  This did not work out as well as I had hoped, so
I would prefer if people made requests via email.  However, I will still accept
merge requests via audit.

As always, we need release testers.  If you are interested, send me an email
with the platform you can test and also subscribe to the release-testers mailing
list:
http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers

Thanks,
Tom
_______________________________________________
cfe-dev mailing list
cfe-dev at lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev

On 22 April 2016 at 23:33, Martin J. O'Riordan via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> What fixes are being proposed for 3.8.1 versus 3.8?
The biggest change is possibly not going in fully, so I'm CC'ing
cfe-dev for a clear picture.

This bug https://llvm.org/bugs/show_bug.cgi?id=23529 reported an issue
with the new GCC ABI for C++11 mangling that wasn't implemented in
Clang due to the complete lack of specification and stabilisation on
GCC's side, but many Linux distributions decided nevertheless to
enable it by default. More importantly, some of them were already
released with Clang 3.8 as the only release they'll ever have
(example, Ubuntu LTS), so if we don't back-port the ABI patches to
3.8.x (whatever x), Ubuntu LTS will not have a working Clang until the
next LTS comes along. AFAIK, many patches were accepted and committed
to implement the ABI change, but all of them are for 3.9, which will
hopefully be out in time for the next Ubuntu (October).

So far, to my knowledge, no ABI patch was proposed to 3.8 yet. Because
of the LTS nature of some Linux distros, this would be relevant even
if *after* 3.9.

> I carefully tracked 3.7 to 3.7.1 one changes, but 3.8 came so close on its
heels that it turned out I shipped 3.8 to my customers and not the 3.7.1 patch.
All the patches I've seem were pretty minimal. Worth of a 3.8.1, if
only early enough to not be made redundant by 3.9.

cheers,
--renato

On Fri, Apr 22, 2016 at 8:29 AM, Tom Stellard via cfe-dev
<cfe-dev at lists.llvm.org> wrote:
> It's about time to start thinking about the 3.8.1 release.  Here
> is a proposed release schedule:
>
> May 25 - Deadline to request a change be merged to the 3.8 branch.
> June 1 - Deadline to merge changes to the 3.8 branch.
> June 1 - 3.8.1-rc1
> June 8 - 3.8.1-rc2 (if necessary)
> June 15 - 3.8.1 Release
>
> If you want a patch included in the 3.8.1 release, send an email
> to llvm-commits with the subject: "3.8 Merge Request: r123456".
> Make sure to cc me and the code owner.  Once you get approval from
> the code owner and me, then you can merge the patch to the 3.8 branch.
> If you don't have commit access or are unable to commit the patch, let
> me know.
>
> For the 3.7.1 release, I encouraged people to make stable patch requests
using
> phabricator's audit tool.  This did not work out as well as I had
hoped,
> so I would prefer if people made requests via email.  However, I will
> still accept merge requests via audit.
>
> As always, we need release testers.  If you are interested, send me an
> email with the platform you can test and also subscribe to the
> release-testers mailing list:
> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
Happy to test and build on Windows as usual.

Cheers,
Hans

I'm onboard for testing x86_64-sles11.3-linux and armhf-linux-vivid.

On Fri, Apr 22, 2016 at 10:29 AM, Tom Stellard via Release-testers <
release-testers at lists.llvm.org> wrote:
> Hi,
>
> It's about time to start thinking about the 3.8.1 release.  Here
> is a proposed release schedule:
>
> May 25 - Deadline to request a change be merged to the 3.8 branch.
> June 1 - Deadline to merge changes to the 3.8 branch.
> June 1 - 3.8.1-rc1
> June 8 - 3.8.1-rc2 (if necessary)
> June 15 - 3.8.1 Release
>
> If you want a patch included in the 3.8.1 release, send an email
> to llvm-commits with the subject: "3.8 Merge Request: r123456".
> Make sure to cc me and the code owner.  Once you get approval from
> the code owner and me, then you can merge the patch to the 3.8 branch.
> If you don't have commit access or are unable to commit the patch, let
> me know.
>
> For the 3.7.1 release, I encouraged people to make stable patch requests
> using
> phabricator's audit tool.  This did not work out as well as I had
hoped,
> so I would prefer if people made requests via email.  However, I will
> still accept merge requests via audit.
>
> As always, we need release testers.  If you are interested, send me an
> email with the platform you can test and also subscribe to the
> release-testers mailing list:
> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>
> Thanks,
> Tom
> _______________________________________________
> Release-testers mailing list
> Release-testers at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>


-- 
-Brian
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20160427/49068924/attachment.html>

On Fri, Apr 22, 2016 at 11:29:39AM -0400, Tom Stellard via cfe-dev
wrote:
> Hi,
> 
> It's about time to start thinking about the 3.8.1 release.  Here
> is a proposed release schedule:
> 
> May 25 - Deadline to request a change be merged to the 3.8 branch.
> June 1 - Deadline to merge changes to the 3.8 branch.
> June 1 - 3.8.1-rc1
> June 8 - 3.8.1-rc2 (if necessary)
> June 15 - 3.8.1 Release
> 
Hi,

Just a reminder that Wednesday is the deadline request changes
be merged to the 3.8 branch.

-Tom
> If you want a patch included in the 3.8.1 release, send an email
> to llvm-commits with the subject: "3.8 Merge Request: r123456".
> Make sure to cc me and the code owner.  Once you get approval from
> the code owner and me, then you can merge the patch to the 3.8 branch.
> If you don't have commit access or are unable to commit the patch, let
> me know.
> 
> For the 3.7.1 release, I encouraged people to make stable patch requests
using
> phabricator's audit tool.  This did not work out as well as I had
hoped,
> so I would prefer if people made requests via email.  However, I will
> still accept merge requests via audit.
> 
> As always, we need release testers.  If you are interested, send me an
> email with the platform you can test and also subscribe to the
> release-testers mailing list:
> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
> 
> Thanks,
> Tom
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev