llvm dev - Dec 2016 - [Openmp-dev] [4.0 Release] Schedule and call for testers

Dear everyone,

There's still plenty of time left, but I'd like to get the schedule
set before folks start disappearing for the holidays.

Note that this release will also switch us to the new versioning
scheme where the major version is incremented for each major release
(i.e., when the 4.0 branch is created, trunk will become 5.0).

If you'd like to help providing binaries and testing for your
favourite platform, please subscribe to the release-testers mailing
list [1].

I propose the following schedule for the 4.0 release:

- 12 January 2017: Create the 4.0 branch. RC1 tagged soon thereafter.

- 1 February: Tag RC2. All lose ends should have been tied up by now.

- 21 February: Final tag. Binaries and release announcement a few days later.

Unless there are any objections, I'll post this on the web page soon.

Cheers,
Hans


  [1] http://lists.llvm.org/mailman/listinfo/release-testers

On 5 December 2016 at 18:26, Hans Wennborg via Release-testers
<release-testers at lists.llvm.org> wrote:
> I propose the following schedule for the 4.0 release:
>
> - 12 January 2017: Create the 4.0 branch. RC1 tagged soon thereafter.
>
> - 1 February: Tag RC2. All lose ends should have been tied up by now.
>
> - 21 February: Final tag. Binaries and release announcement a few days
later.
LGTM.

--renato

On 05 Dec 2016, at 19:26, Hans Wennborg via Openmp-dev <openmp-dev at
lists.llvm.org> wrote:
> 
> There's still plenty of time left, but I'd like to get the schedule
> set before folks start disappearing for the holidays.
> 
> Note that this release will also switch us to the new versioning
> scheme where the major version is incremented for each major release
> (i.e., when the 4.0 branch is created, trunk will become 5.0).
Maybe I didn't pay enough attention, but where is the general outline
for this versioning scheme documented?  And are we still going to do
4.1, 4.2, etc?

> If you'd like to help providing binaries and testing for your
> favourite platform, please subscribe to the release-testers mailing
> list [1].
> 
> I propose the following schedule for the 4.0 release:
> 
> - 12 January 2017: Create the 4.0 branch. RC1 tagged soon thereafter.
> 
> - 1 February: Tag RC2. All lose ends should have been tied up by now.
> 
> - 21 February: Final tag. Binaries and release announcement a few days
later.
> 
> Unless there are any objections, I'll post this on the web page soon.
Note that this is a pretty close follow-up to the 3.9.1 release.  There
is a minor risk of "release burn-out" here... :)

Otherwise, LGTM.

-Dimitry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 194 bytes
Desc: Message signed with OpenPGP using GPGMail
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20161205/5c431a88/attachment.sig>

On Mon, Dec 5, 2016 at 10:42 AM, Dimitry Andric <dimitry at andric.com>
wrote:
> On 05 Dec 2016, at 19:26, Hans Wennborg via Openmp-dev <openmp-dev at
lists.llvm.org> wrote:
>>
>> There's still plenty of time left, but I'd like to get the
schedule
>> set before folks start disappearing for the holidays.
>>
>> Note that this release will also switch us to the new versioning
>> scheme where the major version is incremented for each major release
>> (i.e., when the 4.0 branch is created, trunk will become 5.0).
>
> Maybe I didn't pay enough attention, but where is the general outline
> for this versioning scheme documented?  And are we still going to do
> 4.1, 4.2, etc?
There was a long discussion around the time when the 3.9 branch was
created. I'm planning on writing a blog post to make sure everyone is
up to date.

The idea is that Tom's stable releases will keep incrementing the
"patch" part of the version numbers, just as today, so they would be
4.0.1, 4.0.2, etc.
>> If you'd like to help providing binaries and testing for your
>> favourite platform, please subscribe to the release-testers mailing
>> list [1].
>>
>> I propose the following schedule for the 4.0 release:
>>
>> - 12 January 2017: Create the 4.0 branch. RC1 tagged soon thereafter.
>>
>> - 1 February: Tag RC2. All lose ends should have been tied up by now.
>>
>> - 21 February: Final tag. Binaries and release announcement a few days
later.
>>
>> Unless there are any objections, I'll post this on the web page
soon.
>
> Note that this is a pretty close follow-up to the 3.9.1 release.  There
> is a minor risk of "release burn-out" here... :)
Hopefully 3.9.1 will be done some time before 4.0.0 starts, otherwise
I agree that's not very good for the testers. I don't want to change
the schedule of the major releases though, as we've been on a nice
predictible 6-month cycle for a while now.

Thanks,
Hans

On 5 December 2016 at 18:42, Dimitry Andric via Release-testers
<release-testers at lists.llvm.org> wrote:
> Maybe I didn't pay enough attention, but where is the general outline
> for this versioning scheme documented?  And are we still going to do
> 4.1, 4.2, etc?
This is the thread:

http://lists.llvm.org/pipermail/llvm-dev/2016-June/101044.html

> Note that this is a pretty close follow-up to the 3.9.1 release.  There
> is a minor risk of "release burn-out" here... :)
They're completely different trees, so should only be a problem if we
haven't finished by then.

3.9.1 convergence took a lot longer than expected because of the
number of back-ports. With interest in the point-releases growing, I
think we should try a "half-way" schedule for the point releases, to
make sure that doesn't happen again.

cheers,
--renato

On Mon, 5 Dec 2016 10:26:33 -0800
Hans Wennborg via llvm-dev <llvm-dev at lists.llvm.org> wrote:
> There's still plenty of time left, but I'd like to get the schedule
> set before folks start disappearing for the holidays.
> 
> Note that this release will also switch us to the new versioning
> scheme where the major version is incremented for each major release
> (i.e., when the 4.0 branch is created, trunk will become 5.0).
Will this new version scheme mean that 4.1 (if ever released) will be
ABI-compatible with 4.0? If it will be so, we should update SONAMEs
accordingly.

-- 
Best regards,
Michał Górny
<http://dev.gentoo.org/~mgorny/>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 963 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20161205/1b9ba604/attachment-0001.sig>

On 5 December 2016 at 19:08, Michał Górny via cfe-dev
<cfe-dev at lists.llvm.org> wrote:
> Will this new version scheme mean that 4.1 (if ever released) will be
> ABI-compatible with 4.0? If it will be so, we should update SONAMEs
> accordingly.
Yes. All 4.x will be ABI compatible with 4.0, just like any stable
release we do today. Doesn't matter if it's called 4.0.1 or 4.1.

cheers,
--renato

Hi,
plan looks good to me.
At OpenMandriva, we're already on the 4.0 branch (rev. 287544 right now)
because that's what our next major release (expected in late Q2/early Q3
2017) will ship with.

No big issues here so far, except the LLVMAddAttribute removal (Mesa still
relies on that API -- we've solved it for now by patching it back in).
We'll probably upgrade our snapshot one more time in mid to late December,
then package RC1, RC2 and final (and any RC3 or so that might be added).

In the Android world, we're running daily builds of AOSP master with clang
master inside Linaro. No big issues there either (some extra warnings
emitted by 4.0, esp. address-of-packed-member required some code changes
and/or -Wno-error= workarounds, but that's intentional).

ttyl
bero

On 5 December 2016 at 19:26, Hans Wennborg via Release-testers <
release-testers at lists.llvm.org> wrote:
> Dear everyone,
>
> There's still plenty of time left, but I'd like to get the schedule
> set before folks start disappearing for the holidays.
>
> Note that this release will also switch us to the new versioning
> scheme where the major version is incremented for each major release
> (i.e., when the 4.0 branch is created, trunk will become 5.0).
>
> If you'd like to help providing binaries and testing for your
> favourite platform, please subscribe to the release-testers mailing
> list [1].
>
> I propose the following schedule for the 4.0 release:
>
> - 12 January 2017: Create the 4.0 branch. RC1 tagged soon thereafter.
>
> - 1 February: Tag RC2. All lose ends should have been tied up by now.
>
> - 21 February: Final tag. Binaries and release announcement a few days
> later.
>
> Unless there are any objections, I'll post this on the web page soon.
>
> Cheers,
> Hans
>
>
>   [1] http://lists.llvm.org/mailman/listinfo/release-testers
> _______________________________________________
> Release-testers mailing list
> Release-testers at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20161205/d63df4fe/attachment.html>

I hope you could branch and tag to projects atomically. Are you able?

On Tue, Dec 6, 2016 at 3:26 AM Hans Wennborg via Release-testers <
release-testers at lists.llvm.org> wrote:
> Dear everyone,
>
> There's still plenty of time left, but I'd like to get the schedule
> set before folks start disappearing for the holidays.
>
> Note that this release will also switch us to the new versioning
> scheme where the major version is incremented for each major release
> (i.e., when the 4.0 branch is created, trunk will become 5.0).
>
> If you'd like to help providing binaries and testing for your
> favourite platform, please subscribe to the release-testers mailing
> list [1].
>
> I propose the following schedule for the 4.0 release:
>
> - 12 January 2017: Create the 4.0 branch. RC1 tagged soon thereafter.
>
> - 1 February: Tag RC2. All lose ends should have been tied up by now.
>
> - 21 February: Final tag. Binaries and release announcement a few days
> later.
>
> Unless there are any objections, I'll post this on the web page soon.
>
> Cheers,
> Hans
>
>
>   [1] http://lists.llvm.org/mailman/listinfo/release-testers
> _______________________________________________
> Release-testers mailing list
> Release-testers at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20161206/4a474afd/attachment.html>

It's not atomic, but I specify a specific revision when creating the
branch, across all projects, so it has the same effect.

When creating tags on the branch I just create it on tip-of-tree since
the branch is low traffic.

Does that address your concerns?

On Tue, Dec 6, 2016 at 3:31 AM, NAKAMURA Takumi <geek4civic at gmail.com>
wrote:
> I hope you could branch and tag to projects atomically. Are you able?
>
> On Tue, Dec 6, 2016 at 3:26 AM Hans Wennborg via Release-testers
> <release-testers at lists.llvm.org> wrote:
>>
>> Dear everyone,
>>
>> There's still plenty of time left, but I'd like to get the
schedule
>> set before folks start disappearing for the holidays.
>>
>> Note that this release will also switch us to the new versioning
>> scheme where the major version is incremented for each major release
>> (i.e., when the 4.0 branch is created, trunk will become 5.0).
>>
>> If you'd like to help providing binaries and testing for your
>> favourite platform, please subscribe to the release-testers mailing
>> list [1].
>>
>> I propose the following schedule for the 4.0 release:
>>
>> - 12 January 2017: Create the 4.0 branch. RC1 tagged soon thereafter.
>>
>> - 1 February: Tag RC2. All lose ends should have been tied up by now.
>>
>> - 21 February: Final tag. Binaries and release announcement a few days
>> later.
>>
>> Unless there are any objections, I'll post this on the web page
soon.
>>
>> Cheers,
>> Hans
>>
>>
>>   [1] http://lists.llvm.org/mailman/listinfo/release-testers
>> _______________________________________________
>> Release-testers mailing list
>> Release-testers at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers

On Mon, Dec 5, 2016 at 10:26 AM, Hans Wennborg <hans at chromium.org>
wrote:
> Dear everyone,
>
> There's still plenty of time left, but I'd like to get the schedule
> set before folks start disappearing for the holidays.
>
> Note that this release will also switch us to the new versioning
> scheme where the major version is incremented for each major release
> (i.e., when the 4.0 branch is created, trunk will become 5.0).
There's now a blog post about the new scheme here:
http://blog.llvm.org/2016/12/llvms-new-versioning-scheme.html
> I propose the following schedule for the 4.0 release:
>
> - 12 January 2017: Create the 4.0 branch. RC1 tagged soon thereafter.
>
> - 1 February: Tag RC2. All lose ends should have been tied up by now.
>
> - 21 February: Final tag. Binaries and release announcement a few days
later.
>
> Unless there are any objections, I'll post this on the web page soon.
I've updated the web page.