llvm dev - Dec 2014 - [LLVMdev] [cfe-dev] LLVM 3.6 update

On Tue, Dec 16, 2014 at 3:50 AM, Daniel Sanders
<Daniel.Sanders at imgtec.com> wrote:
> Could we aim for mid/late January? I'd like our target triple problems
to be sorted out for LLVM 3.6 if I can and early-January doesn't leave many
working days to get that finished. Especially given that many people take some
holiday around Christmas and New Year.
>
We generally try to make the releases on a fixed 6-month cycle rather
than wait for features. By this time last year the release was already
in full swing so I don't want to wait much longer.

But, I do want to give folks a chance to return from vacations
(including myself). I think 14 January would be a good date to aim
for.

This would be the tentative schedule:

- 14 January 2015: Branch for 3.6.0 release
  All features should be basically ready. *Minor* changes to complete
things are accepted during Test Phase I.

- 14 January -- 21 January: Testing Phase I
  RC1 binaries are built and tested

- 22 January -- 29 January: Fix bugs from Testing Phase I
  All features should be complete. Any incomplete features need to be
turned off by default.

- 30 January -- 6 Feburary: Testing Phase II
  RC2 binaries are built and tested

- 7 February -- 14 February: Fix bugs from Testing Phase II
  Only critical bug fixes are accepted. The bugs fixed here are
release blockers.

- 21 February: Release 3.6.0.

If this looks OK, I'll post it on the web page.

 - Hans

>> -----Original Message-----
>> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at
cs.uiuc.edu]
>> On Behalf Of Renato Golin
>> Sent: 15 December 2014 18:37
>> To: Hans Wennborg
>> Cc: cfe-dev; llvmdev
>> Subject: Re: [LLVMdev] [cfe-dev] LLVM 3.6 update
>>
>> On 15 December 2014 at 17:44, Hans Wennborg <hans at
chromium.org>
>> wrote:
>> > My tentative plan is to branch early January.
>>
>> That sounds reasonable. I'd say whenever the 3.5.1 finishes we
could start
>> 3.6.
>>
>> cheers,
>> --renato
>> _______________________________________________
>> LLVM Developers mailing list
>> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

> -----Original Message-----
> From: Renato Golin [mailto:renato.golin at linaro.org]
> Sent: 17 December 2014 15:46
> To: Hans Wennborg
> Cc: Daniel Sanders; cfe-dev; llvmdev
> Subject: Re: [LLVMdev] [cfe-dev] LLVM 3.6 update
> 
> On 16 December 2014 at 18:31, Hans Wennborg <hans at chromium.org>
wrote:
> > - 14 January 2015: Branch for 3.6.0 release
> >   All features should be basically ready. *Minor* changes to complete
> > things are accepted during Test Phase I.
> 
> This will give plenty of time, while still not delaying the release too
much.
> 
> 
> > If this looks OK, I'll post it on the web page.
> 
> LGTM.
> 
> thanks,
> --renato
Sounds good to me too.
> From Hans Wennborgs email:
> We generally try to make the releases on a fixed 6-month cycle rather
> than wait for features. By this time last year the release was already
> in full swing so I don't want to wait much longer.
Agreed, it's certainly not a prerequisite and if we miss the date then
we'll have to wait. The reason I'm particularly keen to get this fix
into 3.6 is because it prevents code generation for 64-bit mips targets from the
32-bit mips binaries we currently release. It's possible to work around it
by using clang as a cross-compiler ('-target mips64-linux-gnu') but
that's not supposed to be necessary. It also, removes the need to force the
build triple to 'mips-linux-gnu' when building our 32-bit releases since
the output of config.guess will work.

On Wed, Dec 17, 2014 at 7:46 AM, Renato Golin <renato.golin at linaro.org>
wrote:
> On 16 December 2014 at 18:31, Hans Wennborg <hans at chromium.org>
wrote:
>> - 14 January 2015: Branch for 3.6.0 release
>>   All features should be basically ready. *Minor* changes to complete
>> things are accepted during Test Phase I.
>
> This will give plenty of time, while still not delaying the release too
much.
>
>
>> If this looks OK, I'll post it on the web page.
>
> LGTM.
Thanks! I've posted it.

Tom: should we add a note about 3.5.1 being in progress to the web site?