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 the release, please fix it or file a bugzilla bug, and set the target to 2.0. Any enhancements scheduled for the 2.0 release should go in ASAP. This work should be completed before May 7th. Please try to avoid checking in large changes right before the deadline. I will be creating the 2.0 release branch on May 7th at 9:00PM PST. Reminder of Release Schedule: * 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 you have any questions or concerns, please let me know. -Tanya
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 file a bugzilla > bug, and set the target to 2.0. > > Any enhancements scheduled for the 2.0 release should go in ASAP. This > work should be completed before May 7th. Please try to avoid checking > in large changes right before the deadline.I very much want to get my regalloc refactoring changes in but I don't have a consistent platform to test them on. Someone broke llvm-gcc bootstrapping late last week or this week. Can we please freeze features for a while and get some stability in the tree before we branch 2.0? I really need to test these patches and it seems like the tree has been broken every other day for a week. -Dave
> I very much want to get my regalloc refactoring changes in but I don't > have a consistent platform to test them on. Someone broke llvm-gcc > bootstrapping late last week or this week.How large of a change have you made? With 3 days before the branch creation, I strongly advise people not to be checking in major changes.> Can we please freeze features for a while and get some stability in > the tree before we branch 2.0? I really need to test these patches > and it seems like the tree has been broken every other day for a week.This week has been a bit crazy with people checking in their changes for 2.0. When checking in, people are suppose to be running the llvm-test suite and regression tests. Unfortunately, this doesn't always seem to happen and its hard to control. I know its not a great solution, but you can do preliminary tests with the last stable version of cvs that you (or check the test results to find that date). Creating the branch is a way of freezing the code. If the tree isn't stable on Monday, I will have to make a decision on how to proceed (ie. backing out changes). We may need to change our proceedures for releases in the future. This is how we have done it in the past with no problem, but LLVM is growing much more rapidly now. -Tanya