LLVM 3.6 release notes

It looks like the release notes on trunk are still for 3.5. Can I
rotate that? If not, where are we logging the 3.6 release notes?

Cheers,
Rafael

CC-ing Bill. I think the answer is “yes”, as 3.5 notes should go directly into the branch.

ping.

Bill, where should get 3.6 release notes go?

Yes, commit directly in the 3.5 branch.

About 3.6, we usually reset the release notes after the release (3.5 in
this case).

By the way, clang release notes really need attention.
Many sections are empty (C Language Changes in Clang, C11 Feature Support,
C++ Language Changes in Clang, C++11 Feature Support, etc).

If you are lazy, just send me the information, I will try to write
something.

Sylvestre

The note I have is for 3.6, not 3.5. Should I just hold it until 3.5
is released?

Cheers,
Rafael

That was my understanding! (even if I am not sure I understand why are
doing that).

Sylvestre

No need to hold it. ToT release notes is for 3.6 features.

-bw

This is correct.

-bw