Ted Husted wrote:
On 3/31/06, Don Brown <[EMAIL PROTECTED]> wrote:
Bottom line, the fewer subprojects and even "modules", the quicker a GA
release will happen and the easier the project will be to manage.
Having done the release both ways, I don't see that multiple JARs is a
problem. The work of creating a release is managing the plan, ensuring
that all the relevent issues are resolved, checking the dependencies,
and testing the code. Running the builds is mechanical and easy to
automate.
It isn't the jars I'm talking about, it is the multiple release
processes: the plan, the checklists, the voting, the testing. I'd much
rather do it once on a large project than 6 times on small ones.
As for the risk of being held up, I think that is a much easier risk to
manage. I'm perfectly comfortable with
a) quickly fixing the problem
b) deferring it to the next release
c) backing out the offending code for the release
and each of those operations can take only a few minutes. To assume a
release must have no known issues is not always realistic.
I guess what I'm saying is I'm willing to be the release manager for
1.3.1, but I'm looking to do as little work as possible :)
Don
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
