release procedure updates
git-svn-id: https://svn.apache.org/repos/asf/click/trunk/click@907380 13f79535-47bb-0310-9956-ffa450edef68
diff --git a/documentation/docs/developer-guide/releasing-subprojects.html b/documentation/docs/developer-guide/releasing-subprojects.html
index 7028d58..4288443 100644
--- a/documentation/docs/developer-guide/releasing-subprojects.html
+++ b/documentation/docs/developer-guide/releasing-subprojects.html
@@ -67,6 +67,16 @@
<p/>
For example version <tt>2.2.0</tt> of subproject <tt>ClickIDE</tt> could be published to:
<pre class="codeConfig"><tt>~/public_html/click/clickide/2.2.0</tt></pre>
+ Make sure the uploaded files have the right permissions (<tt>664</tt>)
+ and belong to the 'click' group to ensure that other members
+ have proper access to these files.
+ If not execute the following commands to ensure file and directory
+ permissions are correct:
+ <pre class="codeConfig">ssh people.apache.org
+cd ~/public_html/click/clickide/X.X.X
+find . -type d | xargs chmod 775
+find . -type f | xargs chmod 664
+chgrp -R click *</pre>
</li>
<li>
Verify the digital signatures at <tt>people.apache.org</tt> to
diff --git a/documentation/docs/developer-guide/releasing.html b/documentation/docs/developer-guide/releasing.html
index 5af1df1..f68bc73 100644
--- a/documentation/docs/developer-guide/releasing.html
+++ b/documentation/docs/developer-guide/releasing.html
@@ -158,13 +158,16 @@
<li><tt>click-X.X.X.zip.sha1</tt></li>
<li><tt>click-X.X.X.zip.asc</tt></li>
</ul>
- Make sure the uploaded files have the right permissions (<tt>664</tt>).
+ Make sure the uploaded files have the right permissions (<tt>664</tt>)
+ and belong to the 'click' group to ensure that other members
+ have proper access to these files.
If not execute the following commands to ensure file and directory
permissions are correct:
<pre class="codeConfig">ssh people.apache.org
cd ~/public_html/click/click/X.X.X/dist
find . -type d | xargs chmod 775
-find . -type f | xargs chmod 664</pre>
+find . -type f | xargs chmod 664
+chgrp -R click *</pre>
</li>
<li>
@@ -330,8 +333,8 @@
click-nodeps-X.X.X.pom.asc -> /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/click/click-nodeps/X.X.X/</pre>
</li>
<li>Once the artifacts and POM signatures have been uploaded, execute
- the following commands to ensure the file and directory permissions
- are correct. Note that because of a bug in "maven deploy", all
+ the following commands to ensure the file, directory permissions
+ and group is correct. Note that because of a bug in "maven deploy", all
<tt>maven-metadata.xml*</tt> files must have their permissions set
to 664. (this step must be done for both <tt>snapshots</tt> and <tt>releases</tt>)
@@ -341,7 +344,8 @@
#cd public_html/click/click/X.X.X/maven2
find . ! -perm 775 -type d -user ${USER} -exec chmod 775 {} \;
find . ! -perm 664 -iname maven-metadata.xml* -user ${USER} -exec chmod 664 {} \;
-find . ! -perm 644 ! -iname maven-metadata.xml* -type f -user ${USER} -exec chmod 644 {} \;</pre>
+find . ! -perm 644 ! -iname maven-metadata.xml* -type f -user ${USER} -exec chmod 644 {} \;
+chgrp -R click *</pre>
</li>
<li>Once the artifacts are uploaded you need to verify the signatures:
(this step must be done for both <tt>snapshots</tt> and <tt>releases</tt>)
@@ -388,13 +392,16 @@
rsync -avz --exclude ".svn" ~/temp/click/documentation/ /www/click.apache.org/</pre>
<p/>
- Make sure the website files and folders have the right permissions (<tt>664</tt>).
+ Make sure the website files and folders have the right permissions (<tt>664</tt>)
+ and belong to the 'click' group to ensure that other members
+ have proper access to these files.
If not execute the following commands to ensure file and directory
permissions are correct:
<pre class="codeConfig">ssh people.apache.org
cd /www/click.apache.org/
find . -type d | xargs chmod 776
-find . -type f | xargs chmod 664</pre>
+find . -type f | xargs chmod 664
+chgrp -R click *</pre>
</li>
<li>
Email release announcement to the <tt>user</tt> and <tt>dev</tt>
