similar to: [LLVMdev] LLVM 2.5 Code Freeze 1/21/09

This is just a reminder that the 2.5 code freeze is tomorrow at 9PM PST. Please try to keep the tree stable :) -Tanya

LLVMers, The LLVM 2.2 release code freeze and branch creation is less than 1 month away. All major changes should be commited to svn at least 1 week before the code freeze. As a reminder, here is the complete release schedule (which can also be found on the main page in the right sidebar): Jan 16, 2008: Branch creation/Code Freeze (9PM PST). Jan 18, 2008: First round of pre-release testing

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 2007-12-18, at 20:03, Tanya M. Lattner wrote: > The LLVM 2.2 release code freeze and branch creation is less than 1 > month away. All major changes should be commited to svn at least 1 > week before the code freeze. As a reminder, here is the complete > release schedule (which can also be found on the main page in the > right sidebar): > > Jan 16, 2008: Branch

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

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

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

This is just a reminder that the 2.7 code freeze is coming up very soon. I will create the branch on 3/7 @9pm PST. As we get closer to the code freeze, please do your part to keep the tree as stable as possible. Ideally, we would like to avoid any major changes going in just before the code freeze. So please check in major changes ASAP to ensure adequate testing. Thanks! -Tanya

LLVMers, The LLVM 2.2 code freeze and branch creation is less than 2 weeks away. All major changes should be commited to svn by the middle of next week. As a reminder, here is the complete release schedule (which can also be found on the main page in the right sidebar): Jan 16, 2008: Branch creation/Code Freeze (9PM PST). Jan 18, 2008: First round of pre-release testing begins. Jan 28, 2008:

LLVMers, The LLVM 2.2 code freeze and branch creation is less than 1 week away. At this point, I'm encouraging everyone to think "stability". Please do not check in major changes and please carefully watch all the nightly tester results when commiting any changes at all. As a reminder, here is the complete release schedule (which can also be found on the main page in the right

Please try to limit today's checkins to critical bug fixes. The code freeze/branch creation will happen at 9PM PST. Thanks, Tanya

> On Monday 02 February 2009 13:20, Tanya M. Lattner wrote: >> Just a reminder, I'll be re-creating the 2.5 branch tonight at 9pm PST. > > What does re-creating mean? Why can't the previously-created 2.5 branch > simply be updated? It means deleting the branch and creating a new one. > I ask because svn history will look a little wierd and it makes it harder for

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

Just a reminder, I'll be re-creating the 2.5 branch tonight at 9pm PST. -Tanya

On Monday 02 February 2009 13:20, Tanya M. Lattner wrote: > Just a reminder, I'll be re-creating the 2.5 branch tonight at 9pm PST. What does re-creating mean? Why can't the previously-created 2.5 branch simply be updated? I ask because svn history will look a little wierd and it makes it harder for third parties to track revisions and do merges.

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 code freeze. Since the metadata stuff just settled recently, I like to ask

LLVMers, Tonight is the 2.2 code freeze. I will be creating the branch at 9PM PST. Commit access to SVN will be closed for approximately one hour (or less). I'll send one email before I start the release branch creation and an email when I am finished. If you have any questions, please let me know. Thanks, Tanya Lattner

LLVM Developers, The 2.4 code freeze is October 6th (9PM PDT). By now, all major changes should be checked in and we should be focusing on tree stability. The full release schedule is on the LLVM website. I'll be sending out a final reminder just before branch creation on Monday. If you have any questions, please let me know. Thanks! -Tanya

LLVMers, The 2.5 release branch has been created. You may check it out with the following commands: svn co https://llvm.org/svn/llvm-project/llvm/branches/release_25 svn co https://llvm.org/svn/llvm-project/llvm-gcc-4.2/branches/release_25 svn co https://llvm.org/svn/llvm-project/test-suite/branches/release_25 Please do not commit anything to the release branch. If you have a patch that needs

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.