diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 83568235..a3227a33 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -31,7 +31,8 @@ Here are the steps, which should be automated but aren't (PR welcome!): 1. write release notes in NEWS.md following the format - already in there. commit. + already in there. update README with the new version. + Commit. 2. create a signed git tag "vX.Y.Z" 3. start sbt; `show version` should confirm that the version was taken from the tag @@ -52,8 +53,8 @@ welcome!): (latest/api should be mostly just changed timestamps) 14. push gh-pages 15. log into sonatype website and go through the usual hoops - (search for com.typesafe, verify the artifacts in it, close, - release) + (under Staging Repositories, search for com.typesafe, verify the + artifacts in it, close, release) 16. push the "vX.Y.Z" tag 17. announce release, possibly wait for maven central to sync first diff --git a/README.md b/README.md index c8788f9c..9ec201e2 100644 --- a/README.md +++ b/README.md @@ -106,12 +106,12 @@ You can find published releases on Maven Central. com.typesafe config - 1.3.0 + 1.3.1 sbt dependency: - libraryDependencies += "com.typesafe" % "config" % "1.3.0" + libraryDependencies += "com.typesafe" % "config" % "1.3.1" Link for direct download if you don't use a dependency manager: @@ -766,7 +766,7 @@ Currently the library is maintained against Java 8, but version 1.2.1 and earlier will work with Java 6. Please use 1.2.1 if you need Java 6 support, though some people -have expressed interest in a branch off of 1.3.0 supporting +have expressed interest in a branch off of 1.3.x supporting Java 7. If you want to work on that branch you might bring it up on [chat](https://gitter.im/typesafehub/config). We can release a jar for Java 7 if someone(s) steps up to maintain the branch. The