similar to: [LLVMdev] LLVM 1.9 Release Schedule

LLVMers, It is now 1 week before I will create the 1.9 release branch. I'm asking that all platform maintainers and available llvm developers review the nightly tester results. Please XFAIL any dejagnu tests that are currently failing, fix any warnings, and review the results of the full llvm test suite. If a test failure is determined to be something that needs to be fixed before the

This is just a friendly reminder that the 1.8 release is coming up. Here are the important dates: * July 12, 2006: Email sent out asking platform maintainers to XFAIL tests, check for regression/file bugs, and check in any final stuff for the release. * July 19, 2006: Code freeze and release branch created. Documentation review. * July 26, 2006: Pre-release online for testing * August 2, 2006:

The LLVM project has seen an increase in development over the last year and with all improvements it would be more beneficial to LLVM users to get releases out more frequently (every 3 months). Chris has asked me to send out a time line for the next 2 releases. This approach is different than previous releases. Note that this is just a plan, it is subject to change if it is needed. LLVM 1.8:

LLVM Developers, It is now 1 week before I will create the 2.0 release branch. I'm asking that all platform maintainers and available llvm developers review the nightly tester results. Please XFAIL any dejagnu tests that are currently failing, fix any warnings, and review the results of the full llvm test suite. If a test failure is determined to be something that needs to be fixed before

LLVMers, Sorry for the delay in this email. The 1.8 release has been pushed out 1 week, so today marks 1 week before I create the 1.8 branch. I'm asking that all platform maintainers and available llvm developers review the nightly tester results. Please XFAIL any dejagnu tests that are currently failing, fix any warnings, and review the results of the full llvm test suite. If a test

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.

Hi Tanya, Please apply these patches to the release branch: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of- Mon-20061106/039776.html http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of- Mon-20061106/039781.html Thanks, Evan On Nov 7, 2006, at 10:39 PM, Tanya M. Lattner wrote: > > I created the 1.9 release branch last night. As a reminder, please > do not > check

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

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

I will be creating the branch at 9PM PST. Please refrain from checking in any large changes until after the branch creation. I'm still seeing unexpected dejagnu failures for PPC and X86. Platform maintainers, please XFAIL these and file bugzilla bugs. Email me if you have concerns or questions. -Tanya

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

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

Tanya M. Lattner wrote: > I'm asking that all platform maintainers and available llvm developers > review the nightly tester results. Please XFAIL any dejagnu tests that are > currently failing, fix any warnings, and review the results of the full > llvm test suite. If a test failure is determined to be something that > needs to be fixed before the release, please fix it or

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

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

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

Hi, Tanya! >* November 6, 2006: Code freeze and release branch created. Documentation > revisions. Does it mean that I can commit my changes to LLVM until November 6? Thanks. Tony. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20061030/1e4ae18f/attachment.html>