What about a compromise here. Something as suggested by Martijn & by Johan, but slightly different.
I think that a lot of people may have been playing, or even using one 1.2-SNAPSHOT for their project, because there have been too much time between 1.1 & 1.2. So for them, having a 1.2 quick is a matter of getting a good *identified* dependency for their project. So why not releasing 1.2, without the constructor refactoring, and then ... fiouuu take a deep breath, make the refactoring .... and release 1.3 with the refactoring in the same week. So people almost finishing projects with managers above them saying "where is you 1.2 final" won't be blamed to have used an experimental 1.2 (because they will not have to touch 300 pages), and people wanting to start new projects will use 1.3 instead. But lets face it : if you introduce big API changes, whatever the numbering scheme you use, you will be faced sooner or later to the dilemna of maintaining to (or more) software branches ... or not. On 1/17/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > On 1/17/06, Johan Compagner <[EMAIL PROTECTED]> wrote: > > About youre point. > > Do we have a lot of usecases that that is the case? > > It was just an example. I'm playing devil's advocate here. I want us > to be absolutely sure that /when/ we are going to break, we don't run > into unintended limitations. > > If someone has to update 300+ pages, then we'd be better sure this is > the way to go. We can't make such a change on a whim. > > Martijn > > > > > > On 1/17/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > > > You can't be serious about that... I find the problem that Ari has very > > important. As I mentioned earlier, I think we should take backwards > > compatibility very, very seriously. That means not breaking stuff between > > .x releases. Only when we don't get negative votes, I could envision doing > > an API breaking thing. > > > > > > On a side note, I think we should contemplate the constructor based > > variant before we commit ourselves to it. > > > > > > I can't give a Panel instance as a parameter to a Page constructor anymore > > in the new setup. Was this already thought of? For instance: > > > > > > Panel panel = new BarPanel(someSpecialModel); > > > Page foo = new FooPage(panel); > > > setResponsePage(page); > > > > > > > > > Martijn > > > > > > > > > > > > > > > On 1/17/06, Johan Compagner <[EMAIL PROTECTED]> wrote: > > > > i don't get this. > > > > Then we accumilate MANY MANY more people like that having those problems > > when we release 2.0! > > > > > > > > Or is the idea.. > > > > Release 1.2 for example first of februari and then the 10th of februari > > we have 2.0?? > > > > > > > > because if 2.0 cost only one or 2 months after 1.2 we have a much bigger > > problem with everybody who is > > > > on the 1.2 train. > > > > > > > > i still think now is better. > > > > Break now "everything" and then be done with it. > > > > > > > > johan > > > > > > > > > > > > > > > > > > > > On 1/17/06, Eelco Hillenius < [EMAIL PROTECTED]> wrote: > > > > > Yeah. Fair enough. +1 for 2.0 then. But let's not wait too long with > > > > > releasing 1.2. I think we should finish the session/ pagemap > > > > > refactorings that have been going on, and do a last scan through the > > > > > issues and then release 1.2. and go into maintenance mode for that > > > > > release. And start right away with 2.0 after that. > > > > > > > > > > Eelco > > > > > > > > > > On 1/17/06, Janne Hietamäki < [EMAIL PROTECTED] > wrote: > > > > > > Sounds reasonable. Breaking this on 1.2 would cause too much trouble > > to > > > > > > the users. > > > > > > > > > > > > So, +1 for 2.0 > > > > > > > > > > > > Martijn Dashorst wrote: > > > > > > > +1 with Jonathan. > > > > > > > > > > > > > > > > > > > > > On 1/17/06, *Jonathan Locke* <[EMAIL PROTECTED] > > > > > > > <mailto: [EMAIL PROTECTED]>> wrote: > > > > > > > > > > > > > > > > > > > > > i can understand this predicament and this was my first > > suggestion: > > > > > > > that we release 1.2 as-is and then quickly release a 2.0 with > > these > > > > > > > constructor changes before focusing on a longer-term 2.1... i > > think > > > > > > > your request is a reasonable one and since you object, i'd > > like to > > > > > > > change my vote to match yours. > > > > > > > > > > > > > > -1 for 1.2 > > > > > > > +1 for 2.0 (on a very quick release cycle after 1.2) > > > > > > > > > > > > > > > > > > > -- > > > > > > Janne Hietamäki > > > > > > Cemron Ltd > > > > > > http://www.cemron.com/ > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > This SF.net email is sponsored by: Splunk Inc. Do you grep through > > log files > > > > > > for problems? Stop! Download the new AJAX search engine that makes > > > > > > searching your log files as easy as surfing the web. DOWNLOAD > > SPLUNK! > > > > > > > > http://sel.as-us.falkag.net/sel?cmdlnk&kid3432&bid#0486&dat1642 > > > > > > _______________________________________________ > > > > > > Wicket-develop mailing list > > > > > > Wicket-develop@lists.sourceforge.net > > > > > > > > https://lists.sourceforge.net/lists/listinfo/wicket-develop > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > > files > > > > > for problems? Stop! Download the new AJAX search engine that makes > > > > > searching your log files as easy as surfing the web. DOWNLOAD > > SPLUNK! > > > > > > > http://sel.as-us.falkag.net/sel?cmdlnk&kid3432&bid#0486&dat1642 > > > > > _______________________________________________ > > > > > Wicket-develop mailing list > > > > > Wicket-develop@lists.sourceforge.net > > > > > > > https://lists.sourceforge.net/lists/listinfo/wicket-develop > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Living a wicket life... > > > > > > Martijn Dashorst - http://www.jroller.com/page/dashorst > > > > > > Wicket 1.1 is out: > > http://wicket.sourceforge.net/wicket-1.1 > > > > > > > -- > Living a wicket life... > > Martijn Dashorst - http://www.jroller.com/page/dashorst > > Wicket 1.1 is out: http://wicket.sourceforge.net/wicket-1.1 > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmdlnk&kid3432&bid#0486&dat1642 > _______________________________________________ > Wicket-develop mailing list > Wicket-develop@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wicket-develop > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
