similar to: [LLVMdev] Reminder: 2.5 branch re-creation tonight.

> On Monday 02 February 2009 13:20, Tanya M. Lattner wrote: >> Just a reminder, I'll be re-creating the 2.5 branch tonight at 9pm PST. > > What does re-creating mean? Why can't the previously-created 2.5 branch > simply be updated? It means deleting the branch and creating a new one. > I ask because svn history will look a little wierd and it makes it harder for

On Monday 02 February 2009 13:20, Tanya M. Lattner wrote: > Just a reminder, I'll be re-creating the 2.5 branch tonight at 9pm PST. What does re-creating mean? Why can't the previously-created 2.5 branch simply be updated? I ask because svn history will look a little wierd and it makes it harder for third parties to track revisions and do merges.

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

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!

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

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

LLVMers, I will be creating the 2.3 release branch today at 9PM PDT. During that time, commit access to SVN will be forbidden. I will send out mail shortly before the branch creation, and once it has been completed. Thanks, Tanya

I'll be upgrading the SVN server on llvm.org this Friday from 9pm - whenever I am done. You will notice that all web and of course svn services will be down during this time. Thanks, Tanya

This is just a reminder that I will be creating the 2.0 release branch tonight at 9pm PDT (GMT-7). I'll send out email before and after branch creation. CVS commit access will not be allowed during this time. 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

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

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 testing. Please do your part to keep the tree >> stable in the days leading up to the

This is just a reminder that I will be creating the 1.8 release branch in 1 hour. Please refrain from checking into cvs after 9PM PDT until I send out email confirming the branch has been created. Thanks, Tanya Lattner

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

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

Reminder for all Rails/Ruby Londoners that there is a meet up tonight with guest Chad Fowler. Hope to see some of you there. T -- Posted via http://www.ruby-forum.com/.

On May 9, 5:37 pm, "Tanya M. Lattner" <to... at nondot.org> wrote: > LLVMers, > > I will be creating the 2.3 release branch today at 9PM PDT. During that > time, commit access to SVN will be forbidden. I will send out mail shortly > before the branch creation, and once it has been completed. Hi Tanya, I do not really understand this strict rule :-) While I get it

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

Please try to limit today's checkins to critical bug fixes. The code freeze/branch creation will happen at 9PM PST. Thanks, Tanya