[LLVMdev] RFC: LLVM Release Documentation Changes

[Daniel Dunbar]

On Fri, Feb 25, 2011 at 2:46 PM, Bill Wendling <wendling at apple.com> wrote:
> Hi all,
>
> I'm working up some changes in the way LLVM is released. Attached is the latest HTML file for HowToReleaseLLVM.html. The major change is in how we do branching and tagging. I want to use a hierarchical version of tags for the various release candidates and final release. The structure of the tags would be something like this.
>
> The 2.9 release branch:
>
>        https://llvm.org/svn/llvm-project/llvm/branch/release_29
>
> The 2.9 release candidate 1:
>
>        https://llvm.org/svn/llvm-project/llvm/tags/RELEASE_29/RC1
>
> The 2.9 release candidate 2:
>
>        https://llvm.org/svn/llvm-project/llvm/tags/RELEASE_29/RC2
>
> The 2.9 final release (the one we send out to the public):
>
>        https://llvm.org/svn/llvm-project/llvm/tags/RELEASE_29/Final
>
> Once created, the tags will never change. The branch may change. Though after the final release the branch shouldn't really change.

This seems like a good improvement to me.

> Duncan brought up the question of how to release clang. It would be nice to package clang by itself without all of the LLVM tools. Basically, making it a standalone package. I have no problem with this (in fact, I think it's a great idea), but it does mean changing Makefiles and stuff. Any help with this would be greatly appreciated.

While that would be nice, I doubt it makes sense for 2.9. We probably
need the feature work on the Makefiles etc. to happen on TOT first,
before we consider leveraging that in the release process.

 - Daniel

>
> Comments?
>
> -bw
>
>
>
>
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
>