uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Lally" <ala...@alum.rpi.edu>
Subject Re: [jira] Commented: (UIMA-299) Remove SNAPSHOT from version numbers prior to release
Date Tue, 13 Feb 2007 14:27:07 GMT
On 2/13/07, Michael Baessler (JIRA) <uima-dev@incubator.apache.org> wrote:
>     [ https://issues.apache.org/jira/browse/UIMA-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472627
]
>
> Michael Baessler commented on UIMA-299:
> ---------------------------------------
>
> I think we should only branch if it is really necessary and if we have further development/fixes
on this branch. If we branch now we have to maintain two branches in case of errors until
we do the final release. So my suggestion is that we do the version number change in trunk
and redo it when we have released.
>

OK, I think that makes sense.  Roughly, this is what the maven
"release" plugin will do, though for this release we may want to do it
manually rather than mess with that.  But from its documentation it
says mvn release would do the following:

    * Check that there are no uncommitted changes in the sources
    * Check that there are no SNAPSHOT dependencies
    * Change the version in the poms from x-SNAPSHOT to a new version
(you will be prompted for the versions to use)
    * Transform the SCM information in the POM to include the final
destination of the tag
    * Run the project tests against the modified POMs to confirm
everything is in working order
    * Commit the modified POMs
    * Tag the code in the SCM with a version name (this will be prompted for)
    * Bump the version in the POMs to a new value y-SNAPSHOT (these
values will also be prompted for)
    * Commit the modified POMs


That seems like a good approach to me.

However, we need to update our Eclipse plugin manifest files as well,
as these also contain the version number.  Someday, it might be nice
if these files were updated automatically by the build process,
copying from the POM version.

If it's agreed that our next build should be a release candidate,
should I go ahead and update the version numbers to 2.1.0-incubating
right now?

-Adam

Mime
View raw message