I went through the "unscheduled" bunch of issues looking for reported
2.1 regressions this morning, and in what probably makes a clear
statement about my sanity, cleaned up a number of the 180 issues and
scheduled some for 2.0.x / 2.1 depending on their type (for those that
couldn't be closed out). I expect I missed a few duplicates, etc.
What remains for 2.1-alpha-1 is just the list of regressions, minor
updates, and backwards compatibility documentation (39 issues in
total, though some may be related):
* http://tinyurl.com/5fuwcm
* http://tinyurl.com/6k49gt
I believe we should start to knock these off, and prepare for an alpha
release as is, and wanted to see what others thought.
To cover the inevitable questions:
- Why release now?
163 fixes, 32 months since 2.0. 'Nuff said.
The only thing I care about right now is getting a release out that -
to the best of our knowledge - doesn't have any regressions from
2.0.x. This is really a necessary platform before making further,
bigger changes.
The sooner it gets out, the more time the current changes will have to
be exposed before a final 2.1 release.
- Why not add new feature X first?
There are a bunch of good things going on (I count 8 active feature
branches). As good as each is, none are ready to be merged on to trunk
today, and the time until they are ready is not predictable. Releasing
first doesn't harm the acceptance of these, or ability to make those
changes.
We just need more exposure to the changes that have already been made,
and to narrow down the potential sources of regressions.
So, thoughts?
Cheers,
Brett
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
