Code freeze this friday! (LLVM 2.6/Clang 1.0)

My apologizes for not mailing the clang list with these reminders. I will do better for the 2.7 release. The release plan is a work in progress for Clang, meaning that we will try an approach for this release and then refine it as we learn from what works and what does not. So please, bear with us.

The 2.6 code freeze is this friday, August 21, at 9pm PDT.

All major changes should be checked into SVN at this time. Please
monitor the buildbots closely for any failures.

I ask you to be very cautious with what you commit to svn over the
next few days. This is not the time to be adding experimental code :slight_smile:

What about source information for types, can this go in ?

-Argiris

The 2.6 code freeze is this friday, August 21, at 9pm PDT.

All major changes should be checked into SVN at this time. Please

monitor the buildbots closely for any failures.

I ask you to be very cautious with what you commit to svn over the

next few days. This is not the time to be adding experimental code :slight_smile:

What about source information for types, can this go in ?

Please confirm with Chris. If says its ok, then it can go in.

For situations like this, I generally say if you get permission from the code owner, than its ok. They can evaluate the risk better than I.

-Tanya

The 2.6 code freeze is this friday, August 21, at 9pm PDT.

All major changes should be checked into SVN at this time. Please

monitor the buildbots closely for any failures.

I ask you to be very cautious with what you commit to svn over the

next few days. This is not the time to be adding experimental code :slight_smile:

What about source information for types, can this go in ?

Please confirm with Chris. If says its ok, then it can go in.

For situations like this, I generally say if you get permission from the code owner, than its ok. They can evaluate the risk better than I.

Yes, this is ok, please try to get it in in the next couple days.

-Chris