Skip to content

Latest commit

 

History

History
54 lines (53 loc) · 2.68 KB

release_steps.md

File metadata and controls

54 lines (53 loc) · 2.68 KB

Release steps

  1. Working from a (out of develop) in your fork:
    1. Rev up all 12 pom files to the release version
    2. Build and test it
    3. javadoc
      1. generate javadocs for utilities and extensions-api projects: mvn javadoc:javadoc
      2. place javadocs files under docs/javadocs/<version>
      3. update THREE links in Extension-development-guide.md, pointing to latest javadoc
      4. commit only javadocs Adding javadocs for version x
    4. doc
      1. update zip link (two places in the URL) in Installing-Butterfly.md
    5. sample extension
      1. make sure butterfly.version in tests/sample-extension/pom.xml is updated
      2. place sample-extension jar under docs/jar
      3. update link in QUICK_START.md if jar file name changed
    6. sample app (only if changed)
      1. zip sample-app folder
      2. place updated zip under docs/zip
      3. update link in QUICK_START.md if zip file name changed
    7. Update release notes
    8. Commit Releasing x
    9. Push from to origin (git push origin <temp branch>)
  2. Send and merge PR from origin to upstream develop
  3. Send and merge PR from upstream develop to upstream master
  4. Tag new release from master
    1. Release title should be the version
    2. Add sections New Features and enhancements and Bug fixes from release notes to Release description
  5. Close milestone
    1. Set is due date to today
  6. Deploy artifacts to Maven Central
    1. Go to TravisCI (click on its badge on butterfly repo README)
    2. Click on More Options -> Trigger Build
    3. Set master as branch
    4. Set Releasing <version number> in CUSTOM COMMIT MESSAGE field
    5. Copy and paste the content of .travis_release.yml in CUSTOM CONFIG field
  7. Manual sonatype release
    1. Staging Repositories
    2. Close (the one with sources and everything)
    3. Release
  8. Update Homebrew formula
    1. Update zip link
    2. Update sha256
    3. Verify brew can update or install new version
  9. Working from a (out of develop) in your fork:
    1. Rev up all 12 pom files to the next SNAPSHOT version
    2. Make sure the new Butterfly SNAPSHOT version is set in sample-extension pom file
    3. Build butterlfy-parent and make sure it builds fine
    4. Add new version empty section in release notes
    5. Commit Preparing for version x
    6. Push from to origin (git push origin <temp branch>)
    7. Send and merge PR from origin to upstream develop
  10. Create new milestone
  11. Add issues to new milestone (if any)