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 > they were necessary and we can come up with some solutions. > > 1) It appeared that a component was released even though it hadn't > changed, possibly misled by the fact that the version is bumped > immediately after the last release. If it had changed, there was no easy > way for me to tell. > - solution here is really the maintenance of a changelog or changes > file, but I'd like to discuss what options we have here a little more
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 release still holds true for the JAR produced? If the md5sum is the same then it's not a candidate for release. The POM is packaged up in every JAR so even if the POM changed the md5sum would be different. I guess we need to decide if a change in the metadata is grounds for a release. At first blush I would say yes. > 2) It seemed some releases were needed just to bump a dependency > version. This really shouldn't be necessary as the end application > should be able to select the appropriate versions it wants as long as > they are compatible (though in some cases they may not use that > dependency themselves - so do we need a new construct for that, or > should it simply be included as runtime, or something else?) I think > here we'd benefit from hearing the reasons it was necessary in continuum > or any other examples others can come up with. One that springs to mind > for me is releasing plexus-site-renderer to get a new doxia for the site > plugin. And you needed to do this just to get a new version with some fixes or because the APIs changed? If there were no API changes and just fixes wouldn't the proper use of ranges (and possibly some conventions) allow for this? > Looking forward to hearing your thoughts on these. > > Cheers, > Brett > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org We all have problems. How we deal with them is a measure of our worth. -- Unknown --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
