beta's 1-> x can break api i personally don't care. That happens in
other projects to.
RC everything should be stable.
But if we really need to break one or two things for b2 that we should
do that.
Eelco Hillenius wrote:
Johan Compagner wrote:
b1 doesn't have to be the last beta..
there could be a b2 where we do some other stuff.
Just release it so that people can play with it a bit easier. And
then we will see if we release a RC or one other Beta..
Yes, agreed. We shouldn't have any more API breaks after we release b1
though. Otherwise we should call it alpha :)
I also asked this to find out whether there are open bugs that are
really important for people to have solved in this release. Not
everyone likes to work on cvs (as I do :))
Eelco
just my 2 cents.
johan
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
