> -----Original Message----- > From: sverhagen [mailto:[email protected]] > Sent: Saturday, December 13, 2008 8:31 AM > To: [email protected] > Subject: Re: Up-to-date release > > > > 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.
Unfortunately, I don't believe there is a way to completely ensure an up-to-date work area. A commit could happen just after you do the update so you can still release what is not really in trunk. The only way that I can see you doing what you want would be to do a revision copy of trunk to tags. You just have to be aware that what is in your working copy may not be what actually gets released. I think no matter which way you go, Wendy's advice is still sound. --- Todd Thiessen --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
