Update release-process.md

release-process.md

@@ -18,16 +18,16 @@ Add your sonatype credentials to ~/.sbt/sonatype_credentials
     user=username
     password=password
 
-1. Add changes to the [release notes](release_notes.md) and the versions in the [README](README.md).
-2. run: sbt release release-version <release version> next-version <next release, usually XXX-SNAPSHOT>
-3. (See section 8a https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-7b.StageExistingArtifacts)
-4. Login to the Nexus UI at https://oss.sonatype.org/
-5. Under 'Build Promotion' select Staging Repositories.
-6. Find our release item and click it
-7. Click the Close button (next to the Refresh button)
-8. Wait ...
-9. Keep checking the Activity tab to see if any rules failed.
-10. If that succeeds, select the release again and click 'Release'
-11. Wait ...
-12. Keep checking the Activity tab to see if there are any problems
-13. Look for the release in https://oss.sonatype.org/content/repositories/releases/com/casualmiracles/
+1. run: sbt release release-version <release version> next-version <next release, usually XXX-SNAPSHOT>
+2. (See section 8a https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-7b.StageExistingArtifacts)
+3. Login to the Nexus UI at https://oss.sonatype.org/
+4. Under 'Build Promotion' select Staging Repositories.
+5. Find our release item and click it
+6. Click the Close button (next to the Refresh button)
+7. Wait ...
+8. Keep checking the Activity tab to see if any rules failed.
+9. If that succeeds, select the release again and click 'Release'
+10. Wait ...
+11. Keep checking the Activity tab to see if there are any problems
+12. Look for the release in https://oss.sonatype.org/content/repositories/releases/com/casualmiracles/
+13. Create a release in github with the version and link to differences.