Yepp, nice chat, but who wants to do the dirty work?? The first thing would be to create the 1.4.x branch, then release the current state as wicketstuff 1.4.7, and then modify the settings of the trunk to compile with wicket trunk. Let's split these jobs up to people, then do it. Also maybe we should write some policies about projects and maintaining the projects (like the current maintainers e-mail address should be available in the project pom.xml#developers tag, something like that), but this is an another thread...
Best Regards, Peter 2010-03-19 15:04 keltezéssel, Boris Goldowsky írta: > nino martinez wael wrote: >> I'll be happy to join in Boris. >> > That would be awesome, thanks Nino. > > I'm thinking the first thing would be to bump the wicket dependency to > v1.4.7 and do a maven release of the current state of wicketstuff-core > as version 1.4.7. Make sense? Is that something you could do? > > Stefan Lindner wrote: >> Perhaps we should define an island of stability (like the name >> wickststuff-core implies). > I agree with that & the rest of your message. Jeremy put together a > nice framework under wicketstuff-core, and there are a decent set of > modules in there. How about calling those the stable set. Anyone can > put something into core - as long as it works and they're willing to > make some effort to keep it working. If one of the core modules breaks > with a future wicket version, and no one steps up to fix it, then it > gets dropped out of wicketstuff-core. > >> And: YES, I would help to maintain such a stable core of wicketstuff. > Great!! I think with 4 or 5 people it shouldn't be a terrible task. > (of course I could be wrong...) > > Bng --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
