Given the lackluster release history of Wicket Stuff, I'd suggest going with whatever the only person able *AND* willing to cut releases wants. In this case, that is Jeremy. If you don't want to follow the general Wicket Stuff release processes, you're welcome to maintain your own projects and release them at your own schedule.
It doesn't make sense to me to go back on a decision that was made, just because 2 folks think it is "better". IMO having a release following Wicket's releases is better than not having a release. The problem with Wicket Stuff is not that they follow the Wicket release cycle, it is that nobody gives a damn to cut releases. Jeremy fixed that. If you think you can do better, don't put your project in the Wicket Stuff parent group, but release the software on your own. Martijn On Wed, Aug 12, 2009 at 3:36 PM, Reinhard Nägele<reinhard.naeg...@mgm-tp.com> wrote: > I'd like to second Maartens point. Identical releases to Wicket itself would > mean that it always depends on Wicket. Independent releases would not be > possible. Bugs could not be fixed and new features could not be added > without a new Wicket release. This doesn't really make sense to me. > > Reinhard > > > Jeremy Thomerson schrieb: >>>> >>>> Now that Wicket 1.4.0 is out, I wonder which wicketstuff core version is >>>> compatible. There is no 1.4.0 version of wicketstuff core (yet?). Should >>>> I >>>> use 1.4-rc8-SNAPSHOT? >>>> >> >> It should be just 1.4-SNAPSHOT. 1.4-rc8-SNAPSHOT was an accidental >> relic of after I built rc8 >> >> >>> >>> Side note: I don't see the version of wicket-stuff has to match exactly >>> with version of wicket ? >>> Suppose someone releases wicketstuff-core-1.4.0 today, and tomorrow some >>> bugs are fixed in wicketstuff-core, then we can't release these bug-fixes >>> until wicket 1.4.1 is out ? >>> >>> IMO, wicket is just a dependency of wicketstuff-code (as defoined in the >>> pom) and both projects should use their own unrelated version numbers. >>> >>> wdyt ? >>> >> >> When I setup wicketstuff-core, I proposed that we structure it to have >> identical releases to Wicket. The community agreed. I still think >> this should be the case. >> -- >> Jeremy Thomerson >> http://www.wickettraining.com >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.4 increases type safety for web applications Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.0 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
