[cmake-developers] Preparing for 2.8.11-rc1

Stephen Kelly steveire at gmail.com
Mon Mar 4 11:15:44 EST 2013


On 03/04/2013 02:58 PM, Brad King wrote:
> Stephen,
>
> We originally wanted to start the 2.8.11 release candidate series at
> the end of January.  We've delayed it while your usage requirements
> feature has cooked.  Even last week you were polishing up a few subtle
> corrections, so it was worth the wait.
>
> Normally we try to avoid delaying a new release for a feature still
> under development but this one required such pervasive changes that
> it would have been impractical to develop it on a separate branch.
> Since it is in master we have to wait until it is ready before we
> can release again.  However, there are many other features and bug
> fixes since 2.8.10 for which people are awaiting 2.8.11.
>
> Do you feel the feature has become mature enough for release?  Are
> there any other tests or use cases under development elsewhere on
> which we should wait?

Hi,

I have not tried again to implement a proof of concept of the list 
handling after the discussion about it last week. This week I don't 
think I can commit to it either, but I'm not overly concerned about it 
after the discussion we had. It might make sense to put the unit test 
change from

  https://gitorious.org/~steveire/cmake/steveires-cmake/commit/96ec58003de583794fb7440fc4b3521f272a26d6

in, but then again, the behavior of code like that won't change until 
the next release, and a policy will probably be needed anyway.

I don't have other new tests or features aimed for 2.8.11. It would be 
nice to 'fix' cmGeneratorExpression::Split handling of escaped 
semicolons and square brackets, but I don't think I'll have time to do 
that, and I think it can wait until the following release anyway.

So, I think it's mature enough for release now, yes.

All the best,

Steve.




More information about the cmake-developers mailing list