Hi, Here is schedule for upcoming stable releases: 3.5.2 - This will be the last 3.5.x release. There was a critical bug fix that did not make it into 3.5.1, which made it necessary to do 3.5.2. I will accept other fixes, but the merge window will be very short: March 16 - Tag 3.5.2-rc1 and begin testsing March 25 - 3.5.2 release (If no regressions found during testing). 3.6.1 - Bug fixes for 3.6.1 will now be accepted. If you would to merge a patch into the 3.6 branch, send an email to llvm-commits and cc the code owner and the release manager (me). I will try to periodically send a reminder to the mailing list about the 3.6.1 release, but please do not wait to the last minute to merge your bugfixes. Barring exceptional circumstances, the -rc1 tag date will be firm. May 4 - Tag 3.6.1-rc1 and begin testing May 13 - 3.6.1 release (If no regressions found during testing). -Tom
Hi Tom, Sounds like a plan to me. I particularly welcome the strict schedule. Do we have candidates for 3.6.1 already? Do we want to back-port anything from 3.6.0 to 3.5.2? cheers, --renato On 2 March 2015 at 15:21, Tom Stellard <tom at stellard.net> wrote:> Hi, > > Here is schedule for upcoming stable releases: > > 3.5.2 - This will be the last 3.5.x release. There was a critical bug fix > that did not make it into 3.5.1, which made it necessary to do 3.5.2. I > will accept other fixes, but the merge window will be very short: > > March 16 - Tag 3.5.2-rc1 and begin testsing > March 25 - 3.5.2 release (If no regressions found during testing). > > 3.6.1 - Bug fixes for 3.6.1 will now be accepted. If you would to merge > a patch into the 3.6 branch, send an email to llvm-commits and cc the > code owner and the release manager (me). > > I will try to periodically send a reminder to the mailing list about > the 3.6.1 release, but please do not wait to the last minute to merge > your bugfixes. Barring exceptional circumstances, the -rc1 tag date will > be firm. > > May 4 - Tag 3.6.1-rc1 and begin testing > May 13 - 3.6.1 release (If no regressions found during testing). > > -Tom > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
On Tue, Mar 03, 2015 at 11:31:21AM +0000, Renato Golin wrote:> Hi Tom, > > Sounds like a plan to me. I particularly welcome the strict schedule. > > Do we have candidates for 3.6.1 already? Do we want to back-port > anything from 3.6.0 to 3.5.2? >We do have candidates for 3.6.1. Hans sent me a list and a few other people have nominated patches already. I don't know if there is anything in 3.6.0 that would need to be backported, maybe someone else knows. -Tom> cheers, > --renato > > On 2 March 2015 at 15:21, Tom Stellard <tom at stellard.net> wrote: > > Hi, > > > > Here is schedule for upcoming stable releases: > > > > 3.5.2 - This will be the last 3.5.x release. There was a critical bug fix > > that did not make it into 3.5.1, which made it necessary to do 3.5.2. I > > will accept other fixes, but the merge window will be very short: > > > > March 16 - Tag 3.5.2-rc1 and begin testsing > > March 25 - 3.5.2 release (If no regressions found during testing). > > > > 3.6.1 - Bug fixes for 3.6.1 will now be accepted. If you would to merge > > a patch into the 3.6 branch, send an email to llvm-commits and cc the > > code owner and the release manager (me). > > > > I will try to periodically send a reminder to the mailing list about > > the 3.6.1 release, but please do not wait to the last minute to merge > > your bugfixes. Barring exceptional circumstances, the -rc1 tag date will > > be firm. > > > > May 4 - Tag 3.6.1-rc1 and begin testing > > May 13 - 3.6.1 release (If no regressions found during testing). > > > > -Tom > > > > _______________________________________________ > > LLVM Developers mailing list > > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev