On Thu, May 29, 2008 at 6:39 PM, Michael McCallum <[EMAIL PROTECTED]> wrote:
> release early release often... we don't use snapshot dependencies and > release > artifacts early. So if you are working on one of the 13 dependent libraries > as soon as you - the dev - is happy the change is ready for use then you > release it. why leave it as a snapshot? If the change would break anything > useing it we bump the major version up so its not pulled in until > downstream > users are ready. > > if you use version ranges and manage codelines by major version then you > can > easily have the trunk of a project being actively developed and released > without pulling it into a deliverable. Hmm, interesting perspective. I still find it takes an hour or two to pull off a release, between the dry-run, the actual prepare and the perform -- do you find that cost goes down if you release a lot, or have tricks for reducing the cost of releasing? - Geoffrey -- Geoffrey Wiseman
