-
Notifications
You must be signed in to change notification settings - Fork 187
Release planning
Mark Paluch edited this page May 12, 2017
·
5 revisions
Calendar - Probably most up to date.
- Preparation: Have GPG signing key set up
- Update
repository
inspring-vault-dependencies/pom.xml
to point to the appropriate repository - Create release ticket
- Update changelog
- Update notice.txt to contain the appropriate version
- Run Maven release
- Upload documentation
- For releases deployed to Maven Central: Log into OSS Sonatype and promote staging repo
- Close milestone and create new milestone
- Update project page
Milestone:
mvn release:prepare -Pmilestone,spring -DreleaseProfiles=milestone,spring -DautoVersionSubmodules=true -DdevelopmentVersion=1.0.0.BUILD-SNAPSHOT -DreleaseVersion=1.0.0.RC1 -Dtag=1.0.0.RC1 -DpushChanges=false
git push --tags
mvn release:perform -Pmilestone,spring -DreleaseProfiles=milestone,spring
cd target/checkout
# Create docs
mvn install -Pdistribute
Release:
mvn release:prepare -Pcentral -DreleaseProfiles=central -DautoVersionSubmodules=true -DdevelopmentVersion=1.0.1.BUILD-SNAPSHOT -DreleaseVersion=1.0.0.RELEASE -Dtag=1.0.0.RELEASE -DpushChanges=false
git push --tags
mvn release:perform -Pcentral -DreleaseProfiles=central
cd target/checkout
# Create docs
mvn install -Pdistribute
Docs deployment:
- deploy docs file from spring-vault-distribution/target (spring-vault-(version)-docs.zip) to org/springframework/vault/spring-vault/(version number)
- Assign properties
-
zip.name
=spring-vault
-
zip.type
=docs
-
zip.deployed
=false
-