Skip to main content
Jump to: navigation, search

Difference between revisions of "Californium/Release Process"

(Created page with " === How-to release californium === 1st get a copy of *all* the californium repository: <code> git clone git@github.com:eclipse/californium.element-connector.git git clone...")
 
Line 14: Line 14:
  
 
git clone git@github.com:eclipse/californium.actinium.git
 
git clone git@github.com:eclipse/californium.actinium.git
 
 
</code>
 
</code>
  
Line 33: Line 32:
 
In each repository:
 
In each repository:
 
* set the final version (probably the same as the current one but without "SNAPSHOT")
 
* set the final version (probably the same as the current one but without "SNAPSHOT")
 +
 +
<code>
 
mvn versions:set -DnewVersion=X.Y.Z
 
mvn versions:set -DnewVersion=X.Y.Z
 +
</code>
  
 
* build & sign the artifacts (you need a gpg key)
 
* build & sign the artifacts (you need a gpg key)
Line 80: Line 82:
 
</code>
 
</code>
  
Now connect on the sonatype OSS nexus and close the stating repository if it's fine you will be able to "release" the repository and the artifact will show up in maven central in a few hours.
+
Now connect on the [https://oss.sonatype.org/#stagingRepositories Sonatype OSS Nexus] and close the staging repository. If it's fine you will be able to "release" the repository and the artifact will show up in maven central in a few hours.
Next step is to edit the eclipse project metadata and announce it on the mailing list.
+
Next step is to edit the [https://projects.eclipse.org/projects/technology.californium/governance Eclipse project metadata] and announce it on the mailing list.

Revision as of 01:37, 16 January 2015

How-to release californium

1st get a copy of *all* the californium repository:

git clone git@github.com:eclipse/californium.element-connector.git

git clone git@github.com:eclipse/californium.scandium.git

git clone git@github.com:eclipse/californium.git

git clone git@github.com:eclipse/californium.tools.git

git clone git@github.com:eclipse/californium.actinium.git

You need to process the repository in the correct order:

element-connector

scandium

californium

tools

actinium

In each repository:

  • set the final version (probably the same as the current one but without "SNAPSHOT")

mvn versions:set -DnewVersion=X.Y.Z

  • build & sign the artifacts (you need a gpg key)

mvn clean install -Prelease

  • looks in ./target/ does the artifacts looks nice?
  • check if there is no *-SNAPSHOT in the dependency:

mvn dependency:tree

  • then commit the pom.xml, and tag the release:

git add pom.xml \*/pom.xml

git commit -m "Release X.Y.Z"

git tag "X.Y.Z"

  • publish the artifacts on maven central

mvn deploy -Prelease

  • prepare for the next cycle:

mvn versions:set -DnewVersion=X.Y.Z-SNAPSHOT

git add pom.xml \*/pom.xml

git commit -m "Release X.Y.Z"

  • push the commits

git push && git push --tags

Now connect on the Sonatype OSS Nexus and close the staging repository. If it's fine you will be able to "release" the repository and the artifact will show up in maven central in a few hours. Next step is to edit the Eclipse project metadata and announce it on the mailing list.

Back to the top