[LLVMdev] RFC: LLVM Release Documentation Changes

[Bill Wendling]

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.

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.

Comments?

-bw

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110225/1eb6c4dd/attachment.html>
-------------- next part --------------