!!! 3.2 Release - Release Notes, Documentation, External Projects and the RC3

Hello,

- State of the 3.2 release

Release is progressing as scheduled, RC2 has
been created and is being tested. RC2 sources
and binaries can be downloaded from:

http://llvm.org/pre-releases/3.2/rc2/

- Release notes and documentation

With RC2 the 3.2 release has reached the point
where it is feature complete and we can turn the attention
to updating documentation, especially the release notes!
Most sections of the release notes still need TLC
to bring them up to date.

- External LLVM based projects

There is a growing number of external projects based on LLVM,
some of which are already described in the release notes.
However, I think there are many more that are not mentioned
and I would like to encourage owners of those projects to send me
a short description to be included in the 3.2 release notes.

- Release Candidate 3 (RC3)

RC3 will be created on Wednesday Dec 5th 10 p.m. PST.
Please let me know if there are any patches for release stopping
issues that should be included in the RC3.

Pawel

Are we going to have a mingw release this time?

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

32bitmicro <root@32bitmicro.com> writes:

- Release Candidate 3 (RC3)

RC3 will be created on Wednesday Dec 5th 10 p.m. PST. Please let me
know if there are any patches for release stopping issues that should
be included in the RC3.

Is the fix for 14465 important enough for the 3.2 release? It's an ICE
that I hit in RC1 that's still there in RC2. Benjamin Kramer fixed it in
r169084 on the mainline.

http://llvm.org/bugs/show_bug.cgi?id=14465

32bitmicro <root@32bitmicro.com> writes:

- Release Candidate 3 (RC3)

RC3 will be created on Wednesday Dec 5th 10 p.m. PST. Please let me
know if there are any patches for release stopping issues that should
be included in the RC3.

Is the fix for 14465 important enough for the 3.2 release? It's an ICE
that I hit in RC1 that's still there in RC2. Benjamin Kramer fixed it in
r169084 on the mainline.

I would like to fix 14465 and r169084 has been sent for approval but I
have not heard yet from Chandler.

http://llvm.org/bugs/show_bug.cgi?id=14465

Pawel

Approved. Sorry for the delay.

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?

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,
either let me know what to merge or just do it yourself.

This approach has worked nicely for PPC target by merging r168189 and
r168352 from the trunk into 3.2 release branch r168353.

http://llvm.org/viewvc/llvm-project?view=rev&revision=168353

In any case at this point the above applies only to
documentation changes.

Pawel

Approved. Sorry for the delay.

And committed revision 169290.

Pawel

Alright, can you please pull in r169280?

Alright, can you please pull in r169280?

Committed revision 169297.

Should LLVM sub-projects like SAFECode be listed here? SAFECode is an external project in that it is not integrated into the LLVM/Clang source trees, but it's also an LLVM sub-project.

-- John T.