Releasing 1.0 version check list :
- no issues in jira (OK)
- current version 0.2-SNAPSHOT (OK)
- no commit remaining (OK)
- propose a vote (OK)
- wait (OK)
- collect answers (OK)
- check the answers (OK)
- mail for vote result (OK)
- move to proper (use svn move + pom link to new parent) (OK)
- change in pom for releasing version (OK)
- change parent pom to include in continuous integration -- don't
- change parent pom to include in site deployment -- don't
- use release:prepare (OK)
- use release:perform (OK)
- deploy to staging (OK)
- deploy the site to staging (OK)
- wait for sync (...) (now...) (OK)
- check the syncing and deployed site (OK)
- mail an announcement (do you have a template) (OK)
-------
- svn mv plugin .. (in sandbox dir) (OK)
- svn remove plugin (in sandbox dir) (OK)
- cd .. (OK)
- svn commit -m "promoting foo, etc" plugin mojo-sandbox/plugin (OK)
- cd plugin (OK)
- (edit to point to new parent/version 7) (OK)
- (edit to correct version) (OK)
- svn commit -m "updated pom for release" (OK)
- mvn release:prepare (OK)
- plugin tag name should be plugin-version (sablecc-maven-plugin-2.0) (OK)
- mvn release:perform (OK)
- mvn site:site site:deploy (OK)
- edit mojo site to put link in right place on left side (OK)
- mvn site:site site:deploy in mojo-site (OK)
- email users list that the deed is done and plugin should be available with the next sync (or wait for sync and then announce) (OK)
Labels
1 Comment
Hide/Show CommentsSep 16, 2010
Jesse Glick
This plugin is now obsolete.