Re: thoughts on release process in general

2005-10-25 Thread John Casey
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Comments inline. - -john Brett Porter wrote: | | Hi, | | I was looking over Emmanuel's Continuum release marathon today and | wondered if there were a couple of things we could do to improve the | process. | | Two things stood out for me - maybe Emm

Re: thoughts on release process in general

2005-10-24 Thread Emmanuel Venisse
I've done a lot of release today for use the same groupId in plexus deps (org.codehaus.plexus). This strategy avoided me managing a great number of exclusions in continuum dependencies. I thought one of these depdencency wasn't release since the groupId change in all plexus components. Perhaps

Re: thoughts on release process in general

2005-10-24 Thread Brett Porter
Jason van Zyl wrote: If the production of a JAR was in fact unchanged then I agree that it should not be release again. If that's the case then it would be a best practice to document this but you can't rely on this as sometimes people just won't document things. What if the md5sum for the last r

Re: thoughts on release process in general

2005-10-24 Thread Jason van Zyl
On Mon, 2005-10-24 at 09:05 -0700, Brett Porter wrote: > Hi, > > I was looking over Emmanuel's Continuum release marathon today and > wondered if there were a couple of things we could do to improve the > process. > > Two things stood out for me - maybe Emmanuel can highlight the reasons > the

thoughts on release process in general

2005-10-24 Thread Brett Porter
Hi, I was looking over Emmanuel's Continuum release marathon today and wondered if there were a couple of things we could do to improve the process. Two things stood out for me - maybe Emmanuel can highlight the reasons they were necessary and we can come up with some solutions. 1) It app