[Wicket-develop] Proposal for release change

[Martijn Dashorst]

All,

Now we have the following release structure in the file releases on sourceforge:

These are sourceforge packages
wicket
wicket-examples
wicket-extensions
wicket-spring
wicket-auth
wicket-SNAPSHOTS

Each project has its own package, and I collapsed all example projects into the example package

This structure is quite cumbersome to create releases in, as I need to visit all packages seperately to create a release and assign uploaded files to each.

I would like to restructure this, as I quite enjoyed delivering the snapshots where all distributables come into one package.

The proposed structure would look like the following:

wicket-1.0
wicket-1.1
wicket-1.2
wicket-1.3
wicket-2.0

Each 'major' release would get updates in the form of release packages. As all projects are dependent on one another I figured having extensions, spring, auth and examples in one release package would be pretty straight forward.

So now we have:

Package wicket
wicket-1.0
wicket-1.0.1
wicket-1.0.2
wicket-1.0.3
wicket-1.1
wicket-1.1.1
wicket-1.2-beta2

Package wicket-extensions
wicket-extensions-1.0
wicket-extensions-1.0.1
wicket-extensions-1.0.2
wicket-extensions-1.0.3
wicket-extensions-1.1
wicket-extensions-1.1.1
wicket-extensions-1.2-beta2

etc.

I want to transform this into:

Package wicket-1.0
wicket-1.0
wicket-1.0.1
wicket-1.0.2
wicket-1.0.3
wicket-extensions-1.0
wicket-extensions-1.0.1
wicket-extensions-1.0.2
wicket-extensions-1.0.3

Package wicket-1.1
wicket-1.1
wicket-1.1.1
wicket-extensions-1.1
wicket-extensions-1.1.1

Package wicket-1.2
wicket-1.2-beta2
wicket-extensions-1.2-beta2

etc.

This will mean restructuring the file release structure, but I think it is worth it.

Any comments on the proposed structure?

Martijn


--
Cast your final vote for Wicket in the SourceForge.net 2006 Community Choice Awards!
http://www.wilsonresearch.com/2006/ostgawards06/ostgawards4.php