similar to: [LLVMdev] 1.8 Pre-Release Reminder

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!

I've put the pre-release tar balls here: http://llvm.org/prereleases/1.8/ I'm asking for help to test this release and to review documentation. If anyone can spare some time to help out, I would really appreciate it. The more people that test, the better this release will be. Quick Summary of Important Dates: August 7th - All documentation reviewed and changes checked in. August 8th -

LLVM Developers, The 2.4 code freeze is October 6th (9PM PDT). Please plan to check in any major changes at least one week before this deadline. The full release schedule is on the LLVM website. If you have any questions, please let me know. Thanks! -Tanya

LLVM Developers, Less than 2 weeks to go! The 2.4 code freeze is October 6th (9PM PDT). Please plan to check in any major changes at least one week before this deadline. The full release schedule is on the LLVM website. If you have any questions, please let me know. Thanks! -Tanya

LLVMers, I just wanted to remind everyone that the 2.2 pre-release testing (round 1) ends tomorrow (2/1/08 midnight). Please send your test results to the list by that deadline. Thanks to all who have tested the release so far! -Tanya

LLVM Developers, The 2.4 code freeze is October 6th (9PM PDT). By now, all major changes should be checked in and we should be focusing on tree stability. The full release schedule is on the LLVM website. I'll be sending out a final reminder just before branch creation on Monday. If you have any questions, please let me know. Thanks! -Tanya

> 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

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

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

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

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:

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

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:

The deadline is today! However, I've decided to give all the procrastinators a couple extra days. You have until Wednesday 9/19 at 9:00PM PDT. Thanks, Tanya On Sep 7, 2012, at 12:53 PM, Tanya Lattner wrote: > Just a reminder that we are still accepting proposals!. > > The deadline is less than 2 weeks away, so please send your proposals in as soon as possible. > > Thank

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? I ask because svn history will look a little wierd and it makes it harder for third parties to track revisions and do merges.

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

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

LLVMers, The 2.1 code freeze and branch creation is next Wednesday, September 12th at 9PM PDT. At this point in time, any major changes should be checked in. You are free to still commit changes to the tree, but please be extra cautious in what you commit and monitor the testers on platforms you are not able to test on. We would like things to remain as stable as possible up until the code

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