3.2 Release has branched :T+2 hours

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 require prior approval so
please contact respective code owners found here:

http://llvm.org/docs/DeveloperPolicy.html#code-owners

with all the fixes and patches that you think should go
into the release,

Good testing!

Pawel

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

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.

Should be there. Please let me know if there are any problems with them

Thanks!

Anton, please add release_32 also in;

clang-tools-extra
compiler-rt
dragonegg
libcxxabi
lldb

They have release_32 in svn. I don't know they might be released, though.

And, could you suppress generating refs/heads/svn-tags and prune them for now?
I am sure that orphan branches will stress the llvm.org server to
begin git-pack-ing whole tree.

...Takumi

Should be there

Anton, thanks.

Still there are issues;

  - compiler_rt doesn't have release_32.
  - dragonegg and polly have svn-tags (most of libcxx/svn-tags are not
ill-formed, though)

They are orphan;

  - clang/google/stable
  - libcxx/svn-tags/RELEASE_30
  - llvm/release_16

...Takumi