So for now I am -1 on this issue, until we have collectively and
officially decided what we are going to do with trunk. And for the
record, this is a veto, pending the results of an official vote on the
constructor change. After that has been decided, we need to recast
this vote.

It all comes together at some point though. Whether my vote will go
for ditching 2.0 depends largely on how well our upgrade path for
existing 2.0 users will be. It has to be complete - all features
exception for the constructor change - within a few weeks, not months.
I think that if we want to, we can provide such an upgrade path, but
we'll have to go through some pain for a few weeks, yes. That would be
the price of being stupid enough to start that 2.0 branch that early
anyway.

Eelco

Reply via email to