similar to: [LLVMdev] 2.7 Code Freeze TOMORROW

LLVMers, The LLVM 2.1 code freeze and branch creation will be tomorrow, September 12th at 9PM PDT. This will be my final reminder until the actual branch creation tomorrow. At this point, please be very careful when checking in changes (especially if they may impact platforms you can not test on). Thanks, Tanya Lattner

The 2.6 code freeze is tomorrow, August 21st, at 9pm PDT. Please refrain from checking in any changes that are major or invasive. This is not the time to be checking in as much as you can because you are trying to cram it into the release. Those who do not use caution with what they commit, may find their commit privileges restricted around the next release. I'm going to stress this

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

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

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

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

Good day Tanya, I would just like to clarify this for myself and a few other people who maybe wondering, Does this code freeze apply to; * Clang. * Compiler-RT. Thanks for your time, Best Regards, Edward O'Callaghan. 2009/8/17 Tanya Lattner <lattner at apple.com>: > LLVMers, > > The 2.6 code freeze is this friday, August 21, at 9pm PDT. > > All major changes should

LLVMers, The 2.1 code freeze and branch creation is next Wednesday, September 12th at 9PM PDT. At this point in time, any major changes should be checked in. You are free to still commit changes to the tree, but please be extra cautious in what you commit and monitor the testers on platforms you are not able to test on. We would like things to remain as stable as possible up until the code

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

LLVMers, The 2.6 code freeze is this friday, August 21, at 9pm PDT. All major changes should be checked into SVN at this time. Please monitor the buildbots closely for any failures. I ask you to be very cautious with what you commit to svn over the next few days. This is not the time to be adding experimental code :) Please help us keep LLVM as stable as possible over the next few days.

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

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

LLVM Developers, The 2.4 code freeze is October 6th (9PM PDT). Please plan to check in any major changes at least one week before this deadline. The full release schedule is on the LLVM website. If you have any questions, please let me know. Thanks! -Tanya

LLVM Developers, Less than 2 weeks to go! The 2.4 code freeze is October 6th (9PM PDT). Please plan to check in any major changes at least one week before this deadline. The full release schedule is on the LLVM website. If you have any questions, please let me know. Thanks! -Tanya

LLVMers, It is now one week before the 2.3 code freeze. On Friday, May 9th at 9PM PDT, I will create the 2.3 release branch. ** All developers should check in all major changes today! ** If you are unable to check in your major changes today, please feel free to ask the appropriate LLVM code owner for approval to check it in. They will decide if its worth the risk to check it in so close to

LLVMers, It is a little over one week before the 2.3 code freeze. On Friday, May 9th at 9PM PDT, I will create the 2.3 release branch. ** All developers should check in all major changes by this coming Friday, May 2nd. ** The idea is to minimize risk and keep the tree stabilized for all targets during the week before the release. Ideally, this would mean that only bug fixes get checked