LLVM 3.6 update

Hi all,

Just wanted to give a quick update on the plan for the 3.6 release.

I had hoped to have at least posted a schedule by now, but I also
don't want us to have two releases in flight at the same time, so the
plan is to wait until 3.5.1 is done.

My tentative plan is to branch early January.

Please let me know what you think.

Cheers,
Hans

That sounds reasonable. I'd say whenever the 3.5.1 finishes we could start 3.6.

cheers,
--renato

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.

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

That sounds good to me.
I’d like to get back to the “twice a year” release schedule (w/o necessarily tying it down much tighter than that).

We’ve been slipping to “seven or eight-ish months” over the last few releases.

03 Sep 2014 3.5 (8 mos)
02 Jan 2014 3.4 (6+ mos)
17 Jun 2013 3.3 (6 mos)
20 Dec 2012 3.2 (7 mos)
22 May 2012 3.1 (5+ mos)
01 Dec 2011 3.0 (8 mos)
06 Apr 2011 2.9 (6 mos)
05 Oct 2010 2.8 (5+ mos)
27 Apr 2010 2.7 (6 mos)
23 Oct 2009 2.6 (5+ mos)
02 Mar 2009 2.5

— Marshall

- 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

From: Renato Golin [mailto:renato.golin@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

> - 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.

Thanks! I've posted it.

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

LGTM