svn commit: r1421549 - /isis/site/trunk/content/contributors/release-process.md

[da...@apache.org]

Author: danhaywood
Date: Thu Dec 13 21:34:09 2012
New Revision: 1421549

URL: http://svn.apache.org/viewvc?rev=1421549&view=rev
Log:
isis site : refining release process docs

Modified:
    isis/site/trunk/content/contributors/release-process.md

Modified: isis/site/trunk/content/contributors/release-process.md
URL: http://svn.apache.org/viewvc/isis/site/trunk/content/contributors/release-process.md?rev=1421549&r1=1421548&r2=1421549&view=diff
==============================================================================
--- isis/site/trunk/content/contributors/release-process.md (original)
+++ isis/site/trunk/content/contributors/release-process.md Thu Dec 13 21:34:09 2012
@@ -264,7 +264,7 @@ Next, check that `core` builds independe
 mvn clean install -o
 </pre>
 
-Confirm that the versions of the Isis artifacts now cached in your local repository are correct; there should be no SNAPSHOTs.
+Confirm that the versions of the Isis artifacts now cached in your local repository are correct.
 
 
 ### Sanity check for non-`core` components
@@ -282,6 +282,11 @@ In particular, in the root pom of the co
 &lt;/parent&gt;
 </pre>
 
+{note
+This obviously requires that the core has been released previously.  If you 
+also releasing core at the same time as the component, then you will need to go through the release process for core first, then come back round to release the component.
+}
+
 Next, delete all Isis artifacts from your local Maven repo:
 
 <pre>
@@ -295,11 +300,7 @@ Next, build the component, though withou
 mvn clean install
 </pre>
 
-Confirm that the versions of the Isis artifacts now cached in your local repository are correct (both those pulled down from Maven central repo, as well as those of the component built locally).  There should be no SNAPSHOTs.
-
-{note
-Note that if you want to release both a new version of core and a new version of a component at the same time, then you'll need to build the Isis core locally first; it won't yet be up on Maven central repo to be pulled down.
-}
+Confirm that the versions of the Isis artifacts now cached in your local repository are correct (both those pulled down from Maven central repo, as well as those of the component built locally).  The versions of `core` should not be a SNAPSHOT.