similar to: [LLVMdev] LLVM 3.2 release notes + LLVM Users

Hi All, With 2.9 starting to make its way out into the world, it is time to start poking at the release notes. I plan to make a pass through llvm-commits to cull some of the major changes into bullets, but am already behind and insanely busy with other stuff over the next week. If you have commit access, I'd really appreciate it if you could take a pass through llvm/docs/ReleaseNotes.html

Good day! To get ready for the release, we need to make sure that the list of external open source projects using LLVM 3.0 (file:///Volumes/Sandbox/llvm/llvm.src/docs/ReleaseNotes.html#externalproj) is up to date. Please send me an email with the project's name and a short description of it. Alternatively, if the project was commented out and you would still like to be listed, just tell me

On 2010-10-04 06:43, Chris Lattner wrote: > Hi All, > > I've finished the first draft of the 2.8 release notes: > http://llvm.org/docs/ReleaseNotes.html > > Please feel free to commit improvements and enhancements. There are "a lot" of changes that went into 2.8, but I think I've scraped most of them out of the commits. However, it is also highly likely that I

Another one: Name: SDC - The Stupid D Compiler (https://github.com/bhelyer/SDC) Description: A project seeking to write a self-hosting compiler for the D programming language, without using the frontend of the reference compiler (DMD). Regards, Alex On Tue, Oct 25, 2011 at 3:06 AM, Bill Wendling <wendling at apple.com> wrote: > Good day! > > To get ready for the release, we need

On Tue, Oct 25, 2011 at 5:06 AM, Bill Wendling <wendling at apple.com> wrote: > Good day! > > To get ready for the release, we need to make sure that the list of external open source projects using LLVM 3.0 (file:///Volumes/Sandbox/llvm/llvm.src/docs/ReleaseNotes.html#externalproj) is up to date. Please send me an email with the project's name and a short description of it.

On 12/4/2012 10:14 AM, Justin Holewinski wrote: > What is the procedure for updating the release notes? I've been committing > changes to the trunk version, should I be editing them elsewhere? Or will > the trunk version be merged in? The exact procedure is not spelled out but I think the easiest would be to merge relevant "ReleaseNotes.html" changes from the trunk,

Alright, can you please pull in r169280? On Tue, Dec 4, 2012 at 12:56 PM, Pawel Wodnicki <root at 32bitmicro.com> wrote: > On 12/4/2012 10:14 AM, Justin Holewinski wrote: > > What is the procedure for updating the release notes? I've been > committing > > changes to the trunk version, should I be editing them elsewhere? Or > will > > the trunk version be

On 1/11/2013 7:15 AM, Justin Holewinski wrote: > Removed from trunk. Pawel can decide if its necessary to update the > tarballs. > > Thanks for the report! Apparently git-svn does not delete removed > directories. PTX directories still exists in release_32 branch and RELEASE_32/final. But they are all empty so PTX can not be build. > > > On Fri, Jan 11, 2013 at 1:36

Hi All, I've finished the first draft of the 2.8 release notes: http://llvm.org/docs/ReleaseNotes.html Please feel free to commit improvements and enhancements. There are "a lot" of changes that went into 2.8, but I think I've scraped most of them out of the commits. However, it is also highly likely that I missed something, so if I missed your favorite feature, please speak

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

Dear Pawel and All, Pawel (and other release managers), can you ask the project maintainers for each project whether they want a release branch before creating it next time? Alternatively, can you leave branch creation up to the project maintainers as in the past? Pawel, you created a release_32 branch of SAFECode last night without my consultation. That commit itself is fine since we just

> I can't find any release_32 branch at http://llvm.org/git/llvm.git or http://llvm.org/git/clang.git. Unfortunately, this requires manual grafting, since git-svn does really bad job here. I'm going to work on this tonight. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Should be there. Please let me know if there are any problems with them On Wed, Nov 14, 2012 at 9:19 PM, Anton Korobeynikov <anton at korobeynikov.info> wrote: >> I can't find any release_32 branch at http://llvm.org/git/llvm.git or http://llvm.org/git/clang.git. > Unfortunately, this requires manual grafting, since git-svn does > really bad job here. > > I'm going

Hi all! Please remember to update the release notes! We're getting close to the release date, and we need the notes to be up-to-date. Also, if you have a project which uses LLVM, please send me a blurb about it and I can add it to our "external projects" list (or, if you have commit access, you can add it). Thanks! -bw

What is the procedure for updating the release notes? I've been committing changes to the trunk version, should I be editing them elsewhere? Or will the trunk version be merged in? On Mon, Dec 3, 2012 at 4:12 PM, 32bitmicro <root at 32bitmicro.com> wrote: > Hi, > > > Are we going to have a mingw release this time? > > As far as I know there is no change from 3.1

John, > Dear Pawel and All, > > Pawel (and other release managers), can you ask the project maintainers > for each project whether they want a release branch before creating it > next time? Alternatively, can you leave branch creation up to the > project maintainers as in the past? I think asking project maintainers for a go/no-go for branch creation is a very good idea that

Hi, > Are we going to have a mingw release this time? As far as I know there is no change from 3.1 and Mignw is considered experimental. Incidentally RC2 mingw32 binaries have been uploaded and are available for download and testing. http://llvm.org/pre-releases/3.2/rc2/clang+llvm-3.2rc2-i386-mingw32-EXPERIMENTAL.tar.gz Pawel > > > On Mon, Dec 3, 2012 at 2:54 PM, 32bitmicro

Dear everyone, The in-progress release notes for 3.7 [1,2] make it look like we didn't do very much over the past six months. Obviously that's not the case at all, so let's get them in shape! If you've been thinking "I should probably add this to the release notes at some point", now is the time :-) I have a list below of changes that might be worth mentioning. I

On 11.05.2012, at 22:55, Bill Wendling wrote: > Hi all! > > Please remember to update the release notes! We're getting close to the release date, and we need the notes to be up-to-date. I added some bigger picture notes to http://llvm.org/docs/ReleaseNotes.html this morning, but we're still missing a lot of text, specifically: - clang: clang has it's own release notes

Hi Pawel, PTX already be replaced with NVPTX. However, PTX subdirectory still sit in lib/Target in 3.2 release. Do you think update the release tarball is a good idea? Also could you remove it from the trunk? Thanks. Regards, chenwj -- Wei-Ren Chen (陳韋任) Computer Systems Lab, Institute of Information Science, Academia Sinica, Taiwan (R.O.C.) Tel:886-2-2788-3799 #1667 Homepage: