Johan Compagner wrote:
i really hate that roadmap, really i do.
[...]
So you really want quickly 1.4 after 1.3 and i guess 1.3 is completely in
maintenance mode pretty much directly
because if we start working on 1.5 you really don't want 1.3 anymore
Absolutely. As soon as we've pushed 1.4 out, full steam ahead on 1.5,
with 1.3 very much in bug-fix-only and encouraging people to switch to
1.4 ASAP.
That means that people that all do 1.3 stuff now are going to 1.4 anyway
(especially because it is also not java5 yet again)
Yes. But they get to do a really complicated Model refactor over the
course of a few weeks, rather than Right This Second. If we have an
agreed roadmap, then the users will even see this coming and be able to
make their own mind up as to whether they want to split their upgrade
effort into two chunks, or just wait a little longer 'til 1.4 comes out.
Releasing so quickly is in my eyes a bad thing. And i really don't want to
release as much under the incubating flag
(i sort of already don't want to do that for 1.3!! but i can live with that
if we really really have to)
Another fly in the ointment is that we will need to move to the
org.apache.wicket namespace at some point. If we have both JDK 1.4 and
JDK 1.5 branches that we're trying to keep in sync, merging will be
slightly more annoying due to the import mismatch, although I guess
that's fairly minor.
The main point here is that we probably won't graduate from incubation
until we switch to this namespace. Would people be happy to do this for
1.3? It's a pretty trivial update for people - just global search and
replace on "import wicket." to "import org.apache.wicket." (with the
exception of things in wicket-stuff like the datepicker). We should
maybe start a vote on this. We will certainly have to do it in 1.4, no
matter what that looks like.
so i am -1 on this release cycle.
what you call 1.3 and 1.4 should be in my eyes 1.3 and why you call 1.5 is
in my eyes 1.4.
Yes, that's right. I'm just splitting 1.3 up into two smaller chunks in
an attempt to make things happen sooner and be more manageable. If we
put the model refactor into 1.3 then I reckon it will be ready for
release around about the same time that 1.4 would otherwise be, or
possibly even later.
You see, this split would allow us to parallelise the two things that I
can see taking a while; getting an Apache-grade release out, and having
users migrate to the new Model code.
If we don't parallelise it, I think we'll end up doing things in a more
sequential fashion and the whole process will take longer. Once we have
a good solid release process, rolling out a 1.4 will be negligible
effort. It therefore wouldn't surprise me if it took longer to do a 1.3
with the model change in it than to get to a 1.4 under this proposal.
Of course, if you're happy to delay rolling out a 1.3 beta for yet
another month, then that's fine. I can tell you that I'll be busy
porting my models for a week or so and not testing things/writing build
code if we push the refactor in right now. :(
Give people a big chunk and let that sink in for quite a while. Dont go
releasing like a mad man.
I'm not convinced. Release early, release often.
BTW, I'm on holiday the week from 19th -> 26th, so won't be around to
help with releases and things during that time.
Al
