Igor Vaynberg wrote:
why should all wicket-stuff projects follow the same release schedule?
all these projects are owned by different people, their only thing in
common being the svn repository.
Technically you are right. But I think there is more to it, than just
only technique.
More than once I looked at wicket-stuff and thought, 'What a big dirty
sandbox'
Having contributed some code in there I often thought of cleaning that
sandbox up, to allow the code to live in a prettier neighborhood. Or to
pull the code out of there and let it live alone, maybe in its own
sourceforge project.
Why didn't I do it yet? Laziness and fear!
For the first option I'm to lazy to dive into all those pom.xml's and
possibly having to dive into some code too. And my fear is that I or the
ideas I'd propose might lack authority. People might yell at me.
For the second option, it is not that hard to set up a new sourceforge
project, than the code would be in a shiny neighborhood but all alone by
itself. So I fear I might have to advertise otherwise it might loose
attention.
So currently I'm following the third option. Leave it as it is and
concentrate on making my contribution shine a little more.
This is my standpoint as an individual, lurching in and around the
wicket community.
But maybe it is time to work on the wicket-stuff community esp. the
wicket-stuff comitters.
I wouldn't mind dividing the wicket-stuff projects into two groups where
one group follows the wicket release schedule and the other ones have
their own. Something like in wicket itself:
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/
branches/
common/
releases/
sandbox/
tags/
trunk/
plus
theuglyrest/
That way also the conforming ones might be build in one teamcity build
plan and the 'uglyrest' might do as they whish.
What I currently don't know what to do about are the projects that claim
to go along with the wicket schedule, but don't, like break the teamcity
build plan. If no one finds himself to heal that broken build, I
wouldn't mind removing them from trunk. They'd still be around in the
branches and releases.
my fifty & a half cent,
mf
-igor
On Wed, May 21, 2008 at 12:58 AM, gumnaam23 <[EMAIL PROTECTED]> wrote:
I would love too. But what confuses me is the aim of wicketstuff projects.
Some of them seem to follow wicket release cycle, some have their own cycle,
and always
build against wicket-trunk.
It would be helpful if wicketstuff projects have a clearer release cycle
plan.
Also some projects use release #s analogues to wicket i.e. 1.3.x and some
use 1.0 and others
0.1 etc.
Wicketstuff projects really could use a proper release cycle and numbering
strategy.
Martijn Dashorst wrote:
or you could volunteer to build those releases for the wicket stuff
projects :D
Martijn
On Tue, May 20, 2008 at 3:35 PM, gumnaam23 <[EMAIL PROTECTED]> wrote:
But then, the wicketstuff maven repository is never deployed with these
builds following the wicket releases.
Everything in the maven repository follows wicket snapshot. This is
really a
pain, I have to maintain a
private wicketstuff code base, just to give the projects proper release
#,
and proper dependency on wicket releases, rather than wicket-SNAPSHOT.
may be someone needs to introduce the "mvn deploy" command to the
wicketstuff developers ;).
Martijn Dashorst wrote:
If you want your project to be used, I think it is wise to do so. A
higher release schedule is also nice, but lower seems to indicate a
bit of a dead end imo.
Martijn
On Tue, May 20, 2008 at 3:13 PM, James Carman
<[EMAIL PROTECTED]> wrote:
So, is the philosophy of wicket-stuff that all of the projects kind of
mirror Wicket's release schedule?
On Tue, May 20, 2008 at 9:06 AM, Martijn Dashorst
<[EMAIL PROTECTED]> wrote:
With that proposal it is very hard to upgrade a version of a project
to a newer version of Wicket. Each maintainer has do create and
maintain the branches. Currently we split off the projects in one go
when we upgrade Wicket.
In an ideal world all projects are constantly rebuilt when Wicket has
an update in core (for a lot of projects this is already the case with
our new teamcity), so maintenance on each project would in most cases
require ensuring api compatibility.
Martijn
On Tue, May 20, 2008 at 2:59 PM, James Carman
<[EMAIL PROTECTED]> wrote:
All,
I was looking at the structure of the wicketstuff.org SVN repository
today and I came up with an idea. Currently, the
wicket-persistence-template project is located at:
http://wicket-stuff.svn.sf.net/svnroot/wicket-stuff/trunk/wicket-persistence-template/
So, all subprojects sort of hang off of the trunk of the root
"wicket-stuff" (should we rename that "wicketstuff"?) trunk. It
would
seem to be better if we let each subproject have their own
trunk/branches/tags triad like this:
http://wicket-stuff.svn.sf.net/svnroot/wicket-stuff/wicket-persistence-template/trunk
http://wicket-stuff.svn.sf.net/svnroot/wicket-stuff/wicket-persistence-template/branches
http://wicket-stuff.svn.sf.net/svnroot/wicket-stuff/wicket-persistence-template/tags
What do you think?
James
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.3 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.3
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.3 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.3
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/-PROPOSAL--wicketstuff-SVN-reorganization...-tp17339733p17340319.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.3 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.3
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/-PROPOSAL--wicketstuff-SVN-reorganization...-tp17339733p17357868.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
