Child pages
  • XmlSchema Release Management
Skip to end of metadata
Go to start of metadata

Committer setup

XmlSchema deploys maven artifacts to the Apache Nexus instance. Committers must have appropriate credentials in their
.m2/settings.xml to deploy snapshots or releases. You will also need a profile named xmlschema_release to specify a few things:


 <profile>
      <id>xmlschema_release</id>
      <properties>
        <deploy.altRepository>ws_commons.releases::default::https://repository.apache.org/service/local/staging/deploy/ws/</deploy.altRepository>
        <gpg.passphrase>my-password</gpg.passphrase>
        <gpg.keyname>bimargulies@apache.org</gpg.keyname>
      </properties>
    </profile>

Deploying snapshots

To deploy a snapshot (Apache committers only), run


mvn deploy -Prelease,fastinstall

That will deploy the latest snapshot along with the javadoc and source jar bundles to apaches snapshot repository.

Performing a release

For the most part, we now follow the same instructions that the maven team uses.
http://maven.apache.org/developers/release/releasing.html

Update the RELEASE-NOTE.txt file, check it in, and and run these commands:


mvn release:prepare -Prelease,xmlschema_release
mvn release:perform

That will tag the release, update the poms, etc, and build it (off the tag) and deploy everything (including source jars, javadoc jars, and distribution zip files)
to the deploy.altRepository location and gpg sign everything.

Next, go to the Nexus repository and 'close' the staging repository.

Next, call the vote(s) based on that.

After the vote passes, you'll need to promote the staging repository.

Also, don't forget to copy the actual distributions to people.apache.org:/www/www.apache.org/dist/ws/commons/XmlSchema.

The site should also be updated (and the present author isn't completely clear on that process yet).

  • No labels