Our priorities should now be:
 - GRADUATE! : get 1.3-incubating-beta1 released and vetted by the ipmc

Why is graduation suddenly the biggest priority now? For me finishing
Wicket in action is a much larger priority to be honest, and getting
rid of two difficult to maintain branches would be a bigger priority
as well.

 - discuss slowly the future of trunk and the roadmap for 1.3 without
powerplays, finger pointing and such. Blame throwing will not help
trunk, nor get us graduated.

I'm sorry, but it looked to me some blame throwing was in place to get
the gravity of the discussion across. IF we decide to ditch 2.0, it's
not going to be a free ride. We would have something to fix, and yes
FAST to not alienate the users working on that.

Until then, I suggest we release 1.3-incubating-beta1 to the ipmc
(doesn't have to go to the general public!) to get our asses out of
the incubator. In the mean time we can discuss whatever is needed to
solve our current problem with trunk. We need to give the discussion
at least another week to get more users involved and their investment
in trunk visible.

Like I said earlier, these things go hand in hand. You can't just say,
we're probably gonna ditch 2.0 without providing an alternative for
those people working on it. Don't forget *we* have been encouraging
people to use 2.0 for their long running projects, so arguments like
'that's what you got working with beta software' just won't do imo.

Until then, no things that we could regret should go into 1.3,
including the model refactor.

Well this is something I don't get: why would we regret it? We won't.
The models got much better, the upgrade possibility is as far as I
know complete and in most cases as easy as removing that parameter.

I want a release first to give people enough stability to do the model
change when they are ready for it. I *don't* want the model change in
another branch (after giving it a good thought) as that other branch
won't happen as soon as it should. Just won't; we have 2.5 years of
experience with the framework to prove that.

Eelco

Reply via email to