Author: schor
Date: Tue Jan 25 20:38:46 2011
New Revision: 1063445
URL: http://svn.apache.org/viewvc?rev=1063445&view=rev
Log:
no Jira - remind to close any open staging repo before starting a new release
candidate
Modified:
uima/site/trunk/uima-website/docs/release.html
uima/site/trunk/uima-website/xdocs/release.xml
Modified: uima/site/trunk/uima-website/docs/release.html
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/docs/release.html?rev=1063445&r1=1063444&r2=1063445&view=diff
==============================================================================
--- uima/site/trunk/uima-website/docs/release.html (original)
+++ uima/site/trunk/uima-website/docs/release.html Tue Jan 25 20:38:46 2011
@@ -451,6 +451,11 @@ mvn install -Papache-release</pre>
LDAP credentials, go to your staging repository, and "close" the
repository. After that,
nothing more can be added. If you deploy another artifact, it will
create a new
staging repository.</p>
+ <p class="note"><b>If you
forget to close the repo</b>, it will be open when you do your next
+ release candidate, and then you'll have in the repo both release
candidates, (with
+ later files overwriting newer), which if any file names have changed, will
<b>create
+ a mess. So be sure to close any previous repo</b> before starting a
release:perform for a new
+ release candidate, so they deploy into a "fresh" empty staging repo.</p>
<p>If you have several
artifacts to release, and you want subsequent artifacts to
depend on the released versions of earlier ones, you can do this, by
releasing the
first one, then releasing subsequent ones that depend on that, etc.
This works because
Modified: uima/site/trunk/uima-website/xdocs/release.xml
URL:
http://svn.apache.org/viewvc/uima/site/trunk/uima-website/xdocs/release.xml?rev=1063445&r1=1063444&r2=1063445&view=diff
==============================================================================
--- uima/site/trunk/uima-website/xdocs/release.xml (original)
+++ uima/site/trunk/uima-website/xdocs/release.xml Tue Jan 25 20:38:46 2011
@@ -242,6 +242,11 @@ mvn install -Papache-release</pre>
LDAP credentials, go to your staging repository, and "close" the
repository. After that,
nothing more can be added. If you deploy another artifact, it will
create a new
staging repository.</p>
+ <p class="note"><b>If you forget to close the repo</b>, it will be open
when you do your next
+ release candidate, and then you'll have in the repo both release
candidates, (with
+ later files overwriting newer), which if any file names have changed, will
<b>create
+ a mess. So be sure to close any previous repo</b> before starting a
release:perform for a new
+ release candidate, so they deploy into a "fresh" empty staging repo.</p>
<p>If you have several artifacts to release, and you want subsequent
artifacts to
depend on the released versions of earlier ones, you can do this, by
releasing the
