On 21/09/2010 3:51 PM, Stuart Sierra wrote:
On Tue, Sep 21, 2010 at 7:32 AM, Mark Derricutt<[email protected]> wrote:
Neat :) Is the plan here to have 61 individual releases/version numbers or
a single release for the entire collection?
61 individual versions was my original plan, but now I'm balking at
the complexity of that. I'm open to suggestions for a reasonable
solution. :)
-S
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
We started out with a single release but gave it up as being too much
work since most of our modules did not change from release to release
since we are releasing fairly often and the functional changes are
reasonably confined.
We have about 60 modules as well and a team of just 3 people.
We made a control sheet with all of the modules and do a preliminary
plan at the start of development of a new release to identify the
modules that change and the ones that will not. This is never perfect
but we keep it up to date as we go along and does give us a document of
the versions of each module making up the release.
We also have separated out the core and the API for the core into
separate projects and they always change. If you aim for upward
compatibility in your core libraries and APIs, then you tend to minimize
the number of modules that have to change.
We are also moving to a service oriented architecture using web services
which also improves stability of the view parts of the application.
In our current release that will go into production this week, only 8 of
the 60 modules have new version numbers and require building.
Three of the 8 are the core modules and the aggregation jar that
includes the core and our utility libraries.
Two are web services and the other 3 are WAR files that implement portlets.
This is not a major release but does add 1 major new function, a new
small portlet and fixes 4 or 5 bugs.
I hope that this helps.
Ron
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
