Wendy Smoak-3 wrote: > > I still tend to favor communication and a quiet period when a release > is going on, as well as keeping a close eye on the commits list to > make sure nothing slips in (or slips _by_, as in this case.) >
We have a distributed team, and we release "often" and "small". Many changes are unrelated but may still be in the same module, and Maven safeguarding an up-to-date work area would just suffice. We have a lot of process and tooling and communication in place, but if it's not needed, it's overhead, and we want to cut it. (Our devs are tangled up in overhead a lot of their time already, so whatever we can cover with improving our tooling is very welcome.) -- View this message in context: http://www.nabble.com/Up-to-date-release-tp20925759p20990217.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
