similar to: [LLVMdev] 2.1 Code Freeze reminder

Displaying 20 results from an estimated 20000 matches similar to: "[LLVMdev] 2.1 Code Freeze reminder"

2009 Aug 18
0
[LLVMdev] Code Freeze this Friday!!!
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
2009 Aug 17
2
[LLVMdev] Code Freeze this Friday!!!
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.
2007 Sep 11
0
[LLVMdev] LLVM 2.1 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
2007 Dec 19
2
[LLVMdev] Reminder: LLVM 2.2 code freeze 1 month away
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
2008 Oct 03
0
[LLVMdev] 2.4 Code Freeze - Oct. 6th (3rd reminder)
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
2010 Feb 15
0
[LLVMdev] [cfe-dev] Reminder: 2.7 code freeze in 1.5 weeks
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
2008 Sep 18
0
[LLVMdev] 2.4 Code Freeze Reminder - Oct. 6th
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
2008 Sep 24
0
[LLVMdev] Oct 6th - 2.4 Code Freeze (2nd reminder)
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
2007 Aug 20
0
[LLVMdev] LLVM 2.1 Code Feeze - 9/12/2007
LLVMers, This is just a reminder that the LLVM 2.1 code freeze and branch creation will be September 12, 2007 (9:00PM PDT). Thats about 3.5 weeks away. The complete release schedule may be found on the LLVM main page in the right sidebar: http://llvm.org/ You can also read my last email about the release: http://lists.cs.uiuc.edu/pipermail/llvmdev/2007-July/010022.html My next reminder will
2008 Jan 10
0
[LLVMdev] 2.2 Code Freeze: 1 Week Left
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
2010 Feb 13
0
[LLVMdev] [cfe-dev] Reminder: 2.7 code freeze in 1.5 weeks
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
2008 Jan 06
0
[LLVMdev] Reminder: LLVM 2.2 code freeze 1 month away
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
2010 Feb 12
2
[LLVMdev] Reminder: 2.7 code freeze in 1.5 weeks
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
2008 Apr 30
0
[LLVMdev] 2.3 Code Freeze Coming Soon!
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
2008 May 02
0
[LLVMdev] 2.3 Code Freeze 1 Week Away!
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
2010 Feb 13
1
[LLVMdev] [cfe-dev] Reminder: 2.7 code freeze in 1.5 weeks
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
2008 Jan 03
0
[LLVMdev] LLVM 2.2 Code Freeze in 2 weeks!
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:
2008 Oct 06
0
[LLVMdev] 2.4 Code Freeze Tonight!
LLVMers, I will be creating the 2.4 branch at 9pm PDT tonight. Please attempt to limit your commits to bug fixes and documentation changes. I'll send out email after the branch creation tonight. Thanks, Tanya
2007 Sep 13
1
[LLVMdev] LLVM 2.1 Branch Creation - 9PM PDT!
LLVMers, I will be creating the branch in 30 minutes (9PM PDT). At that time, I will send out mail announcing SVN commit access is suspended. Those with commit privileges should refrain from committing until I send out mail saying commit access is restored. Thanks, Tanya Lattner
2010 Feb 12
0
[LLVMdev] Reminder: 2.7 code freeze in 1.5 weeks
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