On 6 May 2009, at 21:31, Jim Jagielski wrote:
On May 6, 2009, at 4:20 PM, Graham Leggett wrote:
Jim Jagielski wrote:
I'll stop worrying about 2.2 when 2.4 comes closer to being a
reality.
Not saying that releasing 2.4 isn't worth it, but there have been
stops and
starts all along the way, and I think we need to be clear on what we
expect 2.4 to be. Until then, we have no clear defining line on when
2.4 is "done."
Is there anything additional that we want v2.4 to do over and
above what
it does now?
Well, that's the question, isn't it? I can't align the idea
of trunk being a candidate for 2.4 and trunk being a place for
people to experiment...
What do we want 2.4 to be and do. And how.
Draw a line under instability caused by feature creep?
Won't happen. There's too much momentum behind clustering/
loadbalancing.
So aim to provide a clean API for new developments - Paul's
original proposal? Makes sense if we're in a position to do it.
I don't think it'll cure instability once-and-for-all, but if it can
disentangle that which we have and can clearly anticipate NOW
then we should do it. The last thing we want is to commit
*knowingly* to 2.4 as another generation of "muddling along".
If we branch off 2.4 right now from trunk, and say that this becomes
our next main release, and the idea is to clean up what is there,
and, for new experimental stuff, develop on trunk 1st and then
backport to 2.4, I'll jump right on in, since it means code will
be out and released and *used* sooner!
How about fleshing out new-clean-API *before* branching?
Else work-to-date falls into a state of limbo, while 2.4 (by differing
from trunk) remains under the same instability-pressure as 2.2.
+1 to pquerna: CleanAPI
+1 to wrowe: leave 2.2 to do what it does as a stable release
That leaves the question: what amongst current-trunk looks,
stable and what is clearly experimental? CleanAPI should
provide for both, so the latter can develop as clean modules
over the lifetime of 2.4 without causing instability.
Would Step 1 here be to list what trunk needs over and above
what 2.2 (cleanly) provides?
--
Nick Kew
