Skip to end of metadata
Go to start of metadata

Releasing 1.0 version check list :

  1. no issues in jira (OK)
  2. current version 0.2-SNAPSHOT (OK)
  3. no commit remaining (OK)
  4. propose a vote (OK)
  5. wait (OK)
  6. collect answers (OK)
  7. check the answers (OK)
  8. mail for vote result (OK)
  9. move to proper (use svn move + pom link to new parent) (OK)
  10. change in pom for releasing version (OK)
  11. change parent pom to include in continuous integration -- don't
  12. change parent pom to include in site deployment -- don't
  13. use release:prepare (OK)
  14. use release:perform (OK)
  15. deploy to staging (OK)
  16. deploy the site to staging (OK)
  17. wait for sync (...) (now...) (OK)
  18. check the syncing and deployed site (OK)
  19. mail an announcement (do you have a template) (OK)

-------

  1. svn mv plugin .. (in sandbox dir) (OK)
  2. svn remove plugin (in sandbox dir) (OK)
  3. cd .. (OK)
  4. svn commit -m "promoting foo, etc" plugin mojo-sandbox/plugin (OK)
  5. cd plugin (OK)
  6. (edit to point to new parent/version 7) (OK)
  7. (edit to correct version) (OK)
  8. svn commit -m "updated pom for release" (OK)
  9. mvn release:prepare (OK)
  10. plugin tag name should be plugin-version (sablecc-maven-plugin-2.0) (OK)
  11. mvn release:perform (OK)
  12. mvn site:site site:deploy (OK)
  13. edit mojo site to put link in right place on left side (OK)
  14. mvn site:site site:deploy in mojo-site (OK)
  15. 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
  • None
  1. Sep 16, 2010

    This plugin is now obsolete.