similar to: [LLVMdev] 2.7 Release Status

The 2.7 pre-release2 is available for testing: http://llvm.org/pre-releases/2.7/pre-release2/ Please complete all testing by April 23rd EOD. We are shortening this testing period a bit to get the release out soon since its been delayed so far. The release team has done our qualifications and we think its of high quality and ready to go. As this is the last pre-release, we only accept fixes for

All, There has been a huge lack of response to the release. We need people to help fix regressions and to participate in testing the release. Without this support, I see no reason that the release team should spend their time qualifying a release. We need to get all regressions fixed before 2.7 can continue onto pre-release2. Please take a look at all release blockers:

On Apr 6, 2010, at 1:04 PM, David Greene wrote: > On Tuesday 06 April 2010 14:52:47 Dustin Laurence wrote: >> On 04/06/2010 11:45 AM, Tanya Lattner wrote: >>> While lack of linux testing of the testsuite is a problem, this is >>> not why the release is slipping. We need more people to fix bugs. It >>> can't be the same people fixing the bugs for every

On Tue, 30 Mar 2010 14:09:03 -0700, Tanya Lattner <xzss at ____.com> wrote: > All, > > There has been a huge lack of response to the release. We need people to > help fix regressions and to participate in testing the release. Without > this support, I see no reason that the release team should spend their time > qualifying a release. > > We need to get all

On Tuesday 06 April 2010 14:52:47 Dustin Laurence wrote: > On 04/06/2010 11:45 AM, Tanya Lattner wrote: > > While lack of linux testing of the testsuite is a problem, this is > > not why the release is slipping. We need more people to fix bugs. It > > can't be the same people fixing the bugs for every release. > > > > We need more people in the community to

All, We need to get all regressions fixed before 2.7 can continue onto pre-release2. Please take a look at all release blockers: http://llvm.org/bugs/show_bug.cgi?id=6586 At this point, the release is delayed until further notice. If no bugs get fixed this week, then I see no other solution but to cancel the release or only qualify it for darwin (the only platform that is regression free).

On Feb 12, 2010, at 3:02 PM, Douglas Gregor wrote: > > On Feb 12, 2010, at 8:25 AM, David Greene wrote: > >> On Thursday 11 February 2010 18:17:33 Tanya Lattner wrote: >>> Just a reminder that the 2.7 code freeze is on Feb 21st. >>> >>> All major changes should be committed approximately 1 week before the code >>> freeze to ensure adequate

On Fri, Feb 12, 2010 at 5:48 PM, Daniel Dunbar <daniel at zuster.org> wrote: > I am definitely in favor of this if it is ok with Tanya. > > I hope to spend some time in the next few weeks on tracking down > miscompiles, and it would be great to get Clang to the > "early-but-usable-beta" stage so it makes sense to roll binaries for > 2.7. > > Tanya, I can

Just a reminder that the 2.7 code freeze is on Feb 21st. All major changes should be committed approximately 1 week before the code freeze to ensure adequate testing. Please do your part to keep the tree stable in the days leading up to the code freeze. Thanks! -Tanya 2/21 - Code Freeze (9PM PST) 2/27 - Pre-release1 released & community testing begins 3/6 - Pre-release1 testing ends 3/13

I am definitely in favor of this if it is ok with Tanya. I hope to spend some time in the next few weeks on tracking down miscompiles, and it would be great to get Clang to the "early-but-usable-beta" stage so it makes sense to roll binaries for 2.7. Tanya, I can also do the x86-32-pc-linux release testing if no one else steps up. - Daniel On Fri, Feb 12, 2010 at 3:02 PM, Douglas

We have pushed back the release a couple of weeks. Below is the revised schedule: 3/7 - Code Freeze (9PM PST) 3/13 - Pre-release1 released & community testing begins 3/20 - Pre-release1 testing ends 3/27 - Pre-release2 released & community testing begins 4/3 - Pre-release2 testing ends 4/5 - Release As a reminder, all major changes need to be checked in 1 week before code freeze.

The 2.7 pre-release testing ends tomorrow March 24th (11:59PM PDT). I've updated the 2.7 release schedule to include a one week regression fixing week. This is only for regressions found in 2.7 and not for miscellaneous bug fixes. I will no longer be merging in patches that are not a regression as defined in our release process (http://llvm.org/docs/HowToReleaseLLVM.html#release-qualify).

On Feb 12, 2010, at 8:25 AM, David Greene wrote: > On Thursday 11 February 2010 18:17:33 Tanya Lattner wrote: >> Just a reminder that the 2.7 code freeze is on Feb 21st. >> >> All major changes should be committed approximately 1 week before the code >> freeze to ensure adequate testing. Please do your part to keep the tree >> stable in the days leading up to the

Below is the 2.7 release schedule: 2/21 - Code Freeze (9PM PST) 2/27 - Pre-release1 released & community testing begins 3/6 - Pre-release1 testing ends 3/13 - Pre-release2 released & community testing begins 3/20 - Pre-release2 testing ends 3/22 - Release Please remember that all major changes should be committed approximately 1 week before the code freeze. Thanks, Tanya

On Tuesday 30 March 2010 16:09:03 Tanya Lattner wrote: > Please take a look at all release blockers: > http://llvm.org/bugs/show_bug.cgi?id=6586 5893 is not release-critical according to Doug. 6640 appears to be a test system problem with a patch available (one of the ones you're working on?) Which bugs do you have patches for? I don't want to start looking at something if

On Tuesday 06 April 2010 17:35:00 Tanya Lattner wrote: > >>> We need more people in the community to help and I can't see any way > >>> of sugar coating this message. > > > > AFAICT, the only bugs left are Clang bugs and a Darwin llvm-gfortran bug. > > The Linux bugs have all been triaged and either fixed, have what should > > be a simple

On Oct 21, 2009, at 3:44 PM, Tanya Lattner wrote: > Just a reminder that today is the last day for pre-release2 testing. > Hi Tanya, Attached are the log files for Mac OS X 10.5.8 on PowerPC. There are these failures for clang: ******************** Failing Tests (20): /Volumes/SandBox/2.6/llvm-2.6/tools/clang/test/CodeGen/ always_inline.c

On Mar 30, 2010, at 3:45 PM, David Greene wrote: > On Tuesday 30 March 2010 16:09:03 Tanya Lattner wrote: > >> Please take a look at all release blockers: >> http://llvm.org/bugs/show_bug.cgi?id=6586 > > 5893 is not release-critical according to Doug. > Will take care of this. > 6640 appears to be a test system problem with a patch available (one of the >

On Mar 30, 2010, at 4:04 PM, David Greene wrote: > On Tuesday 30 March 2010 17:45:16 David Greene wrote: >> On Tuesday 30 March 2010 16:09:03 Tanya Lattner wrote: >>> Please take a look at all release blockers: >>> http://llvm.org/bugs/show_bug.cgi?id=6586 >> >> 5893 is not release-critical according to Doug. >> >> 6640 appears to be a test

Just a reminder that today is the last day for pre-release2 testing. Thanks, Tanya