Re: Release process for 2.18 cancelled

[Trevor Daniels]

David Kastrup Monday, March 18, 2013 8:52 AM
> 
> It turns out that the pent-up pressure to get forward-looking changes
> into the master branch that have transitory user interfaces or extensive
> changes of internals not exposed to sufficient testing is already too
> high to permit a prerelease phase focused on arriving at stable release
> quality.
> 
> So a release process of 2.18 managed by me is off.  In the current
> situation, I don't consider it realistic that we will be able to make a
> stable release with sufficient reliability in the next four months at
> least, likely longer.

It's a pity, but I think you're right.  But during that four months or
longer we need to be vigilant to prevent any potentially disruptive
changes entering master.  Encouraging or requiring developers to 
use branches for anything other than tidying up or bugfixes from
now onwards seems desirable to me.

Trevor