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.> -----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
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
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
LGTM On Tue, Dec 16, 2014 at 10:31 AM, Hans Wennborg <hans at chromium.org> wrote:> 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 > > _______________________________________________ > cfe-dev mailing list > cfe-dev at cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20141217/9f737c5c/attachment.html>