That's a fair question. This may very well be a "Doc, it hurts when I do X", "Well, dont' do X" case.
However, we currently have things set up to include the Maven version in UI for one of the web components, so that would still say SNAPSHOT, whereas doing a real-release would help indicate the version running to a tester, and be consistent with what we want in a full release. And the version number, even just in jar files, is a lot easier to see in the file name than opening up the manifest to see an SVN attribute that I configure to be added. I will think through whether we should skip the beta release process, but I'd like to hear other suggestions as well... -Stephen On Thu, Jul 17, 2008 at 10:08 AM, nicolas de loof <[EMAIL PROTECTED]> wrote: > Why don't you test the snapshots ? You can configure a cron to deploy > nightly-buils, and SNAPSHOTS to have a unique timestamp number. You can > also > configure the cron to tag if required, or (simplier IMHO) to include the > SVN > revision in MANIFEST files. > > Nicolas > > 2008/7/17 Stephen Duncan Jr <[EMAIL PROTECTED]>: > > > On Thu, Jul 17, 2008 at 9:40 AM, nicolas de loof <[EMAIL PROTECTED]> > > wrote: > > > > > For comparable use case I use the release:stage goal (in place of > > > release:perform) to create the release but not remove the "rolback" > > files. > > > I > > > can then create a 1.0 release to get tested, and return to 1.0-SNAPSHOT > > if > > > some issues are found. I just have to rename the tag from 1.0 to > 1.0-rcX > > > (or > > > delete it). > > > > > > Nicolas > > > > > > > I think our usage is a bit different. These beta builds are used on a > test > > environment for multi-day testing. And for some, I even know there will > be > > changes before a final release; I just want versioned & tagged releases > to > > report bugs against for the functionality that is completed now, even > > though > > I know, perhaps, that some more issues are being worked on before the > final > > release. > > > > -- > > Stephen Duncan Jr > > www.stephenduncanjr.com > > > -- Stephen Duncan Jr www.stephenduncanjr.com
