Master tracks the latest version of scalaz, branches track previous minor versions. eg. master scalaz 7.3, branches scalaz-7.2 and scalaz-7.1.
When scalaz's minor version changes, create a new branch for the old version.
Master is the master, merge into the other branches to maintain docs and compatibility.
Publish the scaladoc to gh-pages: sbt "doc makeSite ghpagesPushSite"
SNAPSHOT versions have docs generated under /api/master, but release versions are under /api/treelog-x.y.z
For snapshots make sure the version number has a -SNAPSHOT suffix. To release to staging, remove the suffix. In both cases use 'sbt publishSigned'
- Add changes to the release notes.
- run: sbt release release-version next-version <next release, usually XXX-SNAPSHOT>
- (See section 8a https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-7b.StageExistingArtifacts)
- Login to the Nexus UI at https://oss.sonatype.org/
- Under 'Build Promotion' select Staging Repositories.
- Find our release item and click it
- Click the Close button (next to the Refresh button)
- Wait ...
- Keep checking the Activity tab to see if any rules failed.
- If that succeeds, select the release again and click 'Release'
- Wait ...
- Keep checking the Activity tab to see if there are any problems
- Look for the release in https://oss.sonatype.org/content/repositories/releases/com/casualmiracles/