similar to: [LLVMdev] Reminder: 2.7 code freeze in 1.5 weeks

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

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 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 code freeze. Since the metadata stuff just settled recently, I like to ask

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

Hi, I would like to compare 2 lists resulted from a sql query! bu there are different levels, so when I want to do: release1<-sqlQuery(channel,paste("select distinct c.ID,c.Title TitleCrit from category cat, category_criteria cc, criteria c, question_criteria qc, question q, form_question fq, form f, release_form rf, release r, product_release pr, product p where cat.ID=cc.category and

Good news, everybody! It's that time of year again. We are going to release LLVM 2.8! I'm taking over for Tanya to give her a much needed break. I can only hope to perform as well as she has. This is my first time as release manager, so bear with me if things don't go smoothly. This message is mostly to give you an idea of the schedule we're planning on. It's an aggressive

LLVMers, 2.6 pre-release1 is ready to be tested by the community. http://llvm.org/prereleases/2.6/ You will notice that we have quite a few pre-compiled binaries (of both clang and llvm-gcc). We have identified several bugs that will be fixed in pre-release2, so please search the bug database before filing a new bug. If you have time, I'd appreciate anyone who can help test the

Tanya Lattner wrote: > LLVMers, > > 2.6 pre-release1 is ready to be tested by the community. > http://llvm.org/prereleases/2.6/ > > You will notice that we have quite a few pre-compiled binaries (of > both clang and llvm-gcc). We have identified several bugs that will be > fixed in pre-release2, so please search the bug database before filing > a new bug. > >

We have pushed back the release a couple of weeks. Below is the revised schedule: 3/7 - Code Freeze (9PM PST) 3/13 - Pre-release1 released & community testing begins 3/20 - Pre-release1 testing ends 3/27 - Pre-release2 released & community testing begins 4/3 - Pre-release2 testing ends 4/5 - Release As a reminder, all major changes need to be checked in 1 week before code freeze.

The 2.7 pre-release testing ends tomorrow March 24th (11:59PM PDT). I've updated the 2.7 release schedule to include a one week regression fixing week. This is only for regressions found in 2.7 and not for miscellaneous bug fixes. I will no longer be merging in patches that are not a regression as defined in our release process (http://llvm.org/docs/HowToReleaseLLVM.html#release-qualify).

On 2009-08-31 08:50, Tanya Lattner wrote: > LLVMers, > > 2.6 pre-release1 is ready to be tested by the community. > http://llvm.org/prereleases/2.6/ > Hi Tanya, Here are the results for x86_64 Linux (Debian unstable): > You will notice that we have quite a few pre-compiled binaries (of > both clang and llvm-gcc). We have identified several bugs that will be > fixed in

Below is the 2.7 release schedule: 2/21 - Code Freeze (9PM PST) 2/27 - Pre-release1 released & community testing begins 3/6 - Pre-release1 testing ends 3/13 - Pre-release2 released & community testing begins 3/20 - Pre-release2 testing ends 3/22 - Release Please remember that all major changes should be committed approximately 1 week before the code freeze. Thanks, Tanya

Hi Tanya, The sources weren't updated for this pre-release testing. So I had the same problems on PPC. -bw On Sun, Aug 30, 2009 at 10:50 PM, Tanya Lattner<lattner at apple.com> wrote: > LLVMers, > 2.6 pre-release1 is ready to be tested by the community. > http://llvm.org/prereleases/2.6/ > You will notice that we have quite a few pre-compiled binaries (of both > clang

> Clang C++ only gets one big coming-out party (ever); a little > more time will make a big difference. Hmm, wouldn't that speak against jamming this into 2.7 ? Let 2.7 go out and don't bark at it's C++ status. That gives you a full release-cycle to get C++ into some *REALLY* good state. For example, a state where you can not just say "Oh, Firefox doesn't crash

On Mon, Feb 15, 2010 at 9:30 AM, Holger Schurig <holgerschurig at gmail.com>wrote: > > Clang C++ only gets one big coming-out party (ever); a little > > more time will make a big difference. > > Hmm, wouldn't that speak against jamming this into 2.7 ? Let 2.7 > go out and don't bark at it's C++ status. That gives you a full > release-cycle to get C++

Greetings! This is the revised LLVM 2.8 release schedule: 9/3 - Branch 9/6 - Pre-release1 out (binaries and tar balls), testing begins 9/12 - Pre-release1 testing ends 9/20 - Pre-release2 testing begins 9/26 - Pre-release2 testing ends 9/28 - Release! There will be more information as the branch date approaches. Please have all major features finished as soon as possible. It's important to

On Feb 15, 2010, at 12:30 AM, Holger Schurig wrote: >> Clang C++ only gets one big coming-out party (ever); a little >> more time will make a big difference. > > Hmm, wouldn't that speak against jamming this into 2.7 ? Let 2.7 > go out and don't bark at it's C++ status. That gives you a full > release-cycle to get C++ into some *REALLY* good state.

I apologize for the delay in setting the 2.6 schedule. Please be aware that we are now moving to a ~6 month release cycle. In addition, 2.6 will be our first release that includes Clang. 08/21 - Code freeze 08/28 - Pre-release1 testing begins 09/04 - Pre-release1 testing ends 09/11 - Pre-release2 testing begins 09/18 - Pre-release2 testing ends 09/21 - Release 2.6 For those that emailed me

On Tue, 3 Aug 2010 23:57:05 -0700 Bill Wendling <wendling at apple.com> wrote: > Good news, everybody! > > It's that time of year again. We are going to release LLVM 2.8! I'm > taking over for Tanya to give her a much needed break. I can only > hope to perform as well as she has. This is my first time as release > manager, so bear with me if things don't go