similar to: [LLVMdev] Announcing: LLVM 3.0 Branch in One Week

It's that time again! (Well, it was that time yesterday, but I made a mistake.) The LLVM 2.9 release is now underway! 2.9 Will Be The Last llvm-gcc Release! That's right! It's the end of an era. The llvm-gcc front-end has served us very well over the years, but with the advent of Clang and DragonEgg it is starting to suffer from bit rot. Starting with the 3.0 release, Clang will be

This is a reminder that we will be branching for LLVM 2.9 in one week! 07:00:00 p.m. Sunday March 6, 2011 PST / 03:00:00 a.m. Monday March 7, 2011 GMT What this means for you: Please keep a watch on all of your patches going into mainline. And pay close attention to the buildbots and fix any issues quickly. Also, please try to finish up any last minute feature work. While it won't be the

Hi Bill, Will the 2.9 branch be reflected in the git mirrors? Thanks, Chad On Sun, Feb 27, 2011 at 5:43 PM, Bill Wendling <wendling at apple.com> wrote: > This is a reminder that we will be branching for LLVM 2.9 in one week! > 07:00:00 p.m. Sunday March 6, 2011 PST / 03:00:00 a.m. Monday March 7, 2011 > GMT > What this means for you: > Please keep a watch on all of your

The LLVM 2.8 branches have been created! We will be conducting several rounds of testing of this branch during September. See http://llvm.org/ for a tentative schedule. What this means for you As I mentioned in a previous e-mail, the branch is still open for code submissions. However there are a few rules that we need to adhere to: No new features are allowed, no matter how trivial they may be.

On Mar 8, 2011, at 10:34 AM, Michel Alexandre Salim wrote: > On 03/08/11 04:01, Bill Wendling wrote: >> It's that time again! (Well, it was that time yesterday, but I made a mistake.) The LLVM 2.9 release is now underway! > >> Developers: >> >> Top-of-tree is now open for submissions. The 2.9 release branch and tags are available for you to check out and test.

We have branched for the 3.2 release! Some "sticky reminders": You can get all of the 3.2 code from the appropriate .../branches/release_32/ You can track state of the 3.2 release through so called "Umbrella bug" : http://llvm.org/bugs/show_bug.cgi?id=13893 Hopefully it will not "rain bugs" on us and we will not need it that much! After branching all patches

Hi all, We branched for the 3.1 release! (Yay!) If there are any fixes which you think should go into the release, please contact the code owners (http://llvm.org/docs/DeveloperPolicy.html#owners) so that they can approve the patches. No patches will be accepted into the 3.1 release without prior approval! This should be a great release! :-) -bw

how to get this branch? still svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm? Thank you. On Tue, Apr 17, 2012 at 2:16 PM, Bill Wendling <wendling at apple.com> wrote: > Hi all, > > We branched for the 3.1 release! (Yay!) > > If there are any fixes which you think should go into the release, please > contact the code owners

Not yet. That is, I don't think any have been filed at all for 3.0. I don't know whether to be happy or worried. :-) Any that are regressions should be marked with the 'regression' keyword and be a release blocker. -bw On Oct 20, 2011, at 8:40 AM, Jim Grosbach wrote: > Hi Bill, > > Do we have a list of which PRs have been filed that are considered release blockers?

I can't find any release_32 branch at http://llvm.org/git/llvm.git or http://llvm.org/git/clang.git. /Patrik Hägglund -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Pawel Wodnicki Sent: den 12 november 2012 07:03 To: llvmdev; cfe-dev at cs.uiuc.edu Subject: [LLVMdev] 3.2 Release has branched :T+2 hours We have branched

What was the revision the branch was made from? On Apr 16, 2012, at 11:16 PM, Bill Wendling <wendling at apple.com> wrote: > Hi all, > > We branched for the 3.1 release! (Yay!) > > If there are any fixes which you think should go into the release, please contact the code owners (http://llvm.org/docs/DeveloperPolicy.html#owners) so that they can approve the patches. No

LLVMers, The LLVM 2.2 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. As a reminder, please do not commit patches to the release branch. Please email me with a

https://llvm.org/docs/DeveloperPolicy.html#new-targets says that experimental backends should be supported by an active community, in part by providing build bots and fixing bugs related to the backend. So while it doesn't *explicitly* say things about patches that only break those backends, I think reading the spirit of that policy says that it's the responsibility of the experimental

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

Hi all, Testing for LLVM 3.0 release candidate 1 is now under way! We will soon have binaries available for you to download and try. Those who would like to compile things and try them out for themselves can grab the source tarballs here: http://llvm.org/pre-releases/3.0/ A Word About Patches I neglected to send out instructions on how to get patches into the LLVM 3.0 branch. All patches must

Hi Bill, Do we have a list of which PRs have been filed that are considered release blockers? -Jim On Oct 17, 2011, at 4:33 PM, Bill Wendling wrote: > Hi all, > > Testing for LLVM 3.0 release candidate 1 is now under way! We will soon have binaries available for you to download and try. Those who would like to compile things and try them out for themselves can grab the source

Chad Colgur <colgur at gmail.com> writes: > Will the 2.9 branch be reflected in the git mirrors? I really, really hope this is the case. The official git mirror documentation says it is only trunk because the current branching scheme in not suitable for git. I don't understand why that would be but I'm not a git-svn expert. My very short reading of the git-svn manpage makes

Hello! There is one week left before we branch for the 3.1 release! Please make sure your patches are sound and that you take care of any failures quickly. It's very important that the tree be in a healthy state when we branch. If you are in the middle of some major change, please finish it before the branching occurs. If it's not in a completed state, we may have to remove it from the

On Feb 28, 2011, at 10:01 AM, David A. Greene wrote: > Chad Colgur <colgur at gmail.com> writes: > >> Will the 2.9 branch be reflected in the git mirrors? > > I really, really hope this is the case. The official git mirror > documentation says it is only trunk because the current branching scheme > in not suitable for git. I don't understand why that would be

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