similar to: [LLVMdev] LLVM 2.4 release schedule

The LLVM 2.3 release schedule has been set. Please note that code freeze is a little less than one month away. May 9 - Code freeze and branch creation (9PM PDT) May 12 - First round of pre-release testing begins (tarballs and binaries provided). May 21 - Pre-release testing ends. May 23 - Second round of pre-release testing begins. May 30 - Pre-release testing ends. June 2 - 2.3 Released. If

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

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.

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

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

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

* Jan 21 - Code Freeze/Branch Creation (9PM PST). * Jan 25 - Pre-release 1 testing begins. * Feb 1 - Pre-release 1 testing ends. * Feb 2 - Pre-release 2 testing begins. * Feb 9 - Pre-release 2 testing ends. * Feb 11 - Release. I'll be sending out an email to clarify the release criteria in a couple of days. It will change slightly for this release. Thanks, Tanya

Dear Tanya: > You also have a few CBE failures that I am not seeing. What version > of xcode do you have installed? Xcode 2.4.1 > Can you send me the following files? > SingleSource/Regression/C/Output/2008-01-07-LongDouble.* > SingleSource/Regression/C/Output/PR1386.* OK, I attached those files (llvm-2.2-test-output.tar.gz) Best regards, 2008/1/30, Tanya Lattner <tonic at

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

My test results for the LLVM 2.2 prerelease. === Q. Target === * Mac OS X 10.4.11 * 2 GHz Intel Core 2 Duo * MacBook % uname -a Darwin macbook.local 8.11.1 Darwin Kernel Version 8.11.1: Wed Oct 10 18:23:28 PDT 2007; root:xnu-792.25.20~1/RELEASE_I386 i386 i386 === Q. How you built the release === * objDir != srcDir * Release build * llvm-gcc-4.2 from source

Thanks for testing the release. Overall the test results look decent with a couple exceptions. You also have a few CBE failures that I am not seeing. What version of xcode do you have installed? Can you send me the following files? SingleSource/Regression/C/Output/2008-01-07-LongDouble.* SingleSource/Regression/C/Output/PR1386.* Thanks, Tanya On Jan 26, 2008, at 6:43 AM, Takanori Ishikawa

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

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

What, the deadline is tomorrow?!? The deadline for proposals snuck up on me, and I'm sure many of you forgot as well. Therefore, I am extending the deadline. I have received some great talk proposals, so keep them coming. However, I have very few tutorials, BoFs, posters, or lightening talk proposals. So please, get those proposals in and lets make this year the best developer meeting yet!

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

LLVMers, I'd like to propose the following release schedule for 2.0: * April 30th - 1 week before code freeze warning email. * May 7th - Code freeze and branch creation. * May 14th - Pre-releases available for additional testing. All documentation changes committed to branch and mainline. * May 21st - Release. If anyone has objection to this schedule, please respond to the list and we 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

I apologize for the delay in setting the 2.6 schedule. Please be aware that we are now moving to a ~6 month release cycle. In addition, 2.6 will be our first release that includes Clang. 08/21 - Code freeze 08/28 - Pre-release1 testing begins 09/04 - Pre-release1 testing ends 09/11 - Pre-release2 testing begins 09/18 - Pre-release2 testing ends 09/21 - Release 2.6 For those that emailed me

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