Apparently my statements didn't provide the correct context. s/Wicket Stuff/Wicket Stuff Core/g
I'm not talking about dropping code into sf.net's svn repository. I'm talking about cutting releases. This is and has been a problem for Wicket Stuff projects. Like it or not, Wicket Stuff as a whole is a code dumping ground. Unless you release your code, it isn't finished. I've yet to see consistent releases being performed by any of the projects. My observation may be "Not constructive" but it is a fact. The Wicket Stuff Core project is one of best things that happened to Wicket Stuff, and I give Jeremy my fullest support in organizing those projects in anyway he can. He has asked the community how to cut releases. The community answered and the answer was to follow Wicket releases. There's good reasoning behind this decision. There is little to support the notion that more releases are necessary or even warranted. Yes if your particular project inside Wicket Stuff Core has a bug fix and the release takes a while it is a drag. But consider the fact that if you have your code in good shape, you get releases *for free*! If you want to have your own release schedule, don't put your project inside the Wicket Stuff Core projects, and go ahead to perform your own releases. It's that simple. And if that is "my way or the highway" then so be it. Wicket Stuff Core is for projects that want to adhere to the Wicket Stuff Core rules, set forward by the guy that is actually doing the work. Respect the time of the guy performing the release, don't add unnecessary time or procedures to his schedule and ensure your code is in optimal shape *ALWAYS*. I find it much more constructive to enable Jeremy to have to jump through as few hoops as possible, than to add more hoops. I don't like to spend other people's free time. If you think that is "Not Constructive" so be it. Martijn On Wed, Aug 12, 2009 at 5:49 PM, Maarten Bosteels<mbosteels....@gmail.com> wrote: > Martijn, > > First off: I do appreciate the time and work that Jeremy spends on > wicketstuff > > > On Wed, Aug 12, 2009 at 4:05 PM, Martijn Dashorst < > martijn.dasho...@gmail.com> wrote: > >> 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. > > > Your way or the highway ? > I don't consider your reaction very community-friendly. There *are* other > people contributing to wicket-stuff. > > >> >> >> It doesn't make sense to me to go back on a decision that was made, >> just because 2 folks think it is "better". > > > Until someone opens the discussion, we won't know how many people think it > is "better" to have separate version numbers. > But you seem to want to kill the discussion (and you will probably succeed, > I am giving up already) > > > >> IMO having a release >> following Wicket's releases is better than not having a release. > > > true > > >> >> >> 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. >> > > Not very constructive. > > Regards > Maarten > > >> >> 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 >> >> > -- 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
