I've just updated the version numbers to 2.2.2-incubating-SNAPSHOT.
There's a new script, "changeVersion.xml", which is an "ant" build
script, that will change the version in most of the places where it
needs changing. For those it doesn't do, it echoes a message saying to
remember to manually change the files.
This script takes as input another file, versions.properties. This file
has the "previous" and "new" values of the version, in various forms,
and the value of the "snapshot" suffix.
To do a new change, add some stanzas on the front - I think we should
leave the values already there as a kind of "history" of the version
changes.
-----------
For the release process I think it goes like this:
Change the version - removing "-SNAPSHOT", in this case (the version is
currently set to 2.2.2-SNAPSHOT)
Create a tag per instructions on
http://incubator.apache.org/uima/release#Building%20The%20Release%20Candidate
Build from the tag, sign things, run the RAT report, and put the
candidate artifacts somewhere on people.apache.org, in a private place
(this is not yet documented on our Release page, I think).
Iterate as needed, changing in the trunk (which is versioned at the
release version now, without SNAPSHOT), re-tagging, etc.
etc.
After the release is completed, change the version, incrementing to the
next guessed release number, and adding -SNAPSHOT.
-----------
The signing works as follows (I'm guessing here, so please correct :-) )
For maven deployment, you use the mvn -DsignArtifacts=true source:jar
deploy in the uimaj pom directory. This has the side effect of
rebuilding and rerunning the tests for all the artifacts, and as another
side effect, it generates the checksums (md5 and sha1) for the uploaded
artifacts.
The artifacts being uploaded to apache.org/dist/incubator/uima consist
of the binary assembly, the source assembly, and the eclipse update
site. mvn assembly:assembly executed in the uimaj-distr project creates
these, and adds the checksums as well.
The script signRelease.sh is being updated to (a) no longer generate
checksums (they were in the wrong format, and the assembly:assembly step
already is generated them (in the right format), and (b) gpg sign not
only the artifacts for the source/binary releases, but also those for
the eclipse update site.
The uimaj-distr/target has the source and binary results, and the
uimaj-eclipse-update-site/target/eclipse-update-site has the eclipse
update site result.
-Marshall
-----------
Does this sound right?
-Marshall
