Continue development

README.adoc

@@ -38,10 +38,11 @@ To do a release (.RELEASE, .RC?, .M?):
 . Execute a maven deploy.
 * For a milestone: `USERNAME=<user> PASSWORD=<encrypted password> mvn -Pdistribute,milestone,docs clean deploy`
 * For a release: `USERNAME=<user> PASSWORD=<encrypted password> mvn -Pdistribute,release,docs clean deploy`
-* For a release to maven central: `USERNAME=<user> PASSWORD=<nexus password> mvn -Pdistribute,gpg,central clean deploy -s settings.xml`
+* For a release to maven central: `USERNAME=<user> PASSWORD=<nexus password> mvn -Pdistribute,gpg,central clean deploy -s settings.xml` (At SonaType, *close* and *releases*)
 . Bump up the version in `pom.xml` again to the next BUILD-SNAPSHOT.
 . Commit the change.
-. `git push` (This will push the tagged version along with the release AND the new snapshot commit)
+. `git push`
+. `git push --tags`
 . Inspect handiwork at https://repo.spring.io/ or https://oss.sonatype.org/#stagingRepositories
 
 NOTE: A word about reference documentation. Based upon https://github.com/spring-projects/spring-framework/wiki/gradle-build-and-release-faq#user-content-wiki-docs_schema_dist_publication[this], the `distribute` profile contains an artifactory property that is applied to the ZIP file generated by the `docs` profile. A CRON job will scoop up the zipped up docs and unpack them inside the target location.

pom.xml

@@ -4,7 +4,7 @@
 
 	<groupId>org.springframework.session</groupId>
 	<artifactId>spring-session-data-mongodb</artifactId>
-	<version>2.0.2.RELEASE</version>
+	<version>2.0.3.BUILD-SNAPSHOT</version>
 
 	<name>Spring Session MongoDB</name>
 	<url>https://github.com/spring-projects/spring-session-data-mongodb</url>