similar to: [LLVMdev] 2.3 Branch Creation TODAY!

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

> Hi Tanya, > > I do not really understand this strict rule :-) > While I get it from a CVS perspective, in Subversion > this is simply overkill. For making a branch you simply > select a revision X, do a "svn -rX up", test, > if successful, you do "svn info ." and use the URL > to make a repo -> repo copy: > > svn cp -rX URL BRANCHURL > >

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

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

LLVMers, The 2.6 code freeze is this friday, August 21, at 9pm PDT. All major changes should be checked into SVN at this time. Please monitor the buildbots closely for any failures. I ask you to be very cautious with what you commit to svn over the next few days. This is not the time to be adding experimental code :) Please help us keep LLVM as stable as possible over the next few days.

Just a reminder, please complete your testing by May 21st! Thanks, Tanya ---------- Forwarded message ---------- Date: Tue, 13 May 2008 00:25:41 -0700 From: Tanya Lattner <tonic at nondot.org> To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> Subject: 2.3 Pre-release available for testing LLVMers, The 2.3 pre-release is available for testing:

Just a reminder, I'll be re-creating the 2.5 branch tonight at 9pm PST. -Tanya

LLVMers, The 2.3 branch has been created. I will now begin the pre-release testing and packaging. I will have the pre-release version tarballs and binaries ready on Monday, May 12th. I will ask you all to begin testing at that time. If you need to check out the branch before then, here is the proper command (for llvm): svn co https://llvm.org/svn/llvm-project/llvm/branches/release_23

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 May 19, 2008, at 9:13 PM, Razvan Aciu wrote: > I tested this pre-release on MSVC and I noted that none of the > submitted > patches (mine or others) were applied. > So the llvm 2.3 will not compile out of the box in MSVC? > Please provide me with a link to the patch(s) that need to be applied (llvm-commits archive email). I only apply patches that have been sent to me and

> 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 May 9, 2008, at 12:16 PM, Tanya M. Lattner wrote: > > While you are correct is is not usually a problem, that assumes that > I do > not check in any changes. If I check in X and someone checks in > something > (Y) that should not go into the release, If they are checking in something, trivially, they want it to go into the release. If they didn't want it in,

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 tested this pre-release on MSVC and I noted that none of the submitted patches (mine or others) were applied. So the llvm 2.3 will not compile out of the box in MSVC? Razvan ----- Original Message ----- From: "Tanya M. Lattner" <tonic at nondot.org> To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> Sent: Monday, May 19, 2008 9:00 PM Subject:

Hi Tanya, Are we allowed to patch the release branch yet? 50940 should go in. Evan On May 9, 2008, at 9:37 PM, Tanya Lattner wrote: > LLVMers, > > The 2.3 branch has been created. I will now begin the pre-release > testing and packaging. I will have the pre-release version tarballs > and binaries ready on Monday, May 12th. I will ask you all to begin > testing at that

This is my patch for MSVC 2008 and it was applied by Chris: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20080512/062390.html I tested it and it is ok for the 2.3 release. Razvan ----- Original Message ----- From: "Tanya Lattner" <tonic at nondot.org> To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> Sent: Tuesday, May 20, 2008 7:40 AM

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

LLVMers, The 2.5 pre-release2 is finally available for testing: http://llvm.org/prereleases/2.5/ If you have time, I'd appreciate anyone who can help test the release. Please do the following: 1) Download/compile llvm source, and either compile llvm-gcc source or use llvm-gcc binary (please compile llvm-gcc with fortran if you can). 2) Run make check, send me the testrun.log 3) Run

LLVMers, The LLVM 2.1 release branches have been created! Over the next 2 days, I will be generating the pre-release tar balls. I will send out mail once I am done and then the community pre-release testing will begin. I'll also be sending out detailed instructions and the release schedule. Full svn access is restored. Thanks for your patience! Thanks, Tanya Lattner

> This is my patch for MSVC 2008 and it was applied by Chris: > > http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20080512/062390.html > > I tested it and it is ok for the 2.3 release. I don't believe I can apply this patch. There have been several patches applied recently to TOT to allow MSVC 2005 which I think many people are using. Does this patch mean that one