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 again and again. Please, think twice about what you commit. There will be other releases! What you can do, is take a look at the documentation and see what areas can be improved :) Thanks, Tanya Lattner -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090820/feb35081/attachment.html>
On Thu, Aug 20, 2009 at 10:32 AM, Tanya Lattner<lattner at apple.com> wrote:> 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 again and again. Please, think twice about what you > commit. There will be other releases!To this end, keep track of the build bots: http://google1.osuosl.org:8011/waterfall If they say something failed, pay close attention to it and fix the problem or revert the patch! :-) -bw