click-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sa...@apache.org
Subject svn commit: r731112 - /incubator/click/trunk/click/TODO.txt
Date Sat, 03 Jan 2009 22:34:57 GMT
Author: sabob
Date: Sat Jan  3 14:34:57 2009
New Revision: 731112

URL: http://svn.apache.org/viewvc?rev=731112&view=rev
Log:
updated TODO

Modified:
    incubator/click/trunk/click/TODO.txt

Modified: incubator/click/trunk/click/TODO.txt
URL: http://svn.apache.org/viewvc/incubator/click/trunk/click/TODO.txt?rev=731112&r1=731111&r2=731112&view=diff
==============================================================================
--- incubator/click/trunk/click/TODO.txt (original)
+++ incubator/click/trunk/click/TODO.txt Sat Jan  3 14:34:57 2009
@@ -27,27 +27,31 @@
 4. ant build-distribution
 5. clean deploy to Tomcat and test click-examples
 6. tag release, e.g. click-1.4-RC3
-7. sftp upload click-xxx.zip to sourceforge -> http://alexandria.wiki.sourceforge.net/File+Release+System+-+Offering+Files+for+Download
-8. release file at sourceforge
-9. upload web site
-10. add sourceforge release notes
+7. Digitally sign the click-<version>.zip. Note the -u argument is only necessary if
you have more 1 GPG Key.
+     gpg --armor -u Z1CA11AA --output click-<version>.zip.asc --detach-sig click-<version>.zip
+8. sftp upload click-xxx.zip to people.apache.org:~/public_html/release/<version> and
start the voting process
+9. after voting, publish the distribution to people.apache.org:/www/www.apache.org/dist/incubator/click/click/X.X.X
+10. upload web site
 11. email release announcement to click, velocity and cayenne
 12. update TODO.txt, documentation/header.html, framework/src/click-control.properties, build/build.properties,
examples/src/click-page.properties to the next version
 
 Maven Artifact Upload Procedures
 --------------------------------
-1. Ensure the 'sf.repo' server is setup in ~/.m2/settings.xml, otherwise maven won't authenticate
at sourceforge. For example:
+1. Ensure the 'apache.releases' server is setup in ~/.m2/settings.xml, so maven knows who
is uploading the artifact. For example:
   <settings>
     <servers>
       <server>
-        <id>sf.repo</id>
-        <username>SOURCEFORGE_USERNAME,click</username>
-        <password>SOURCEFORGE_PASSWORD</password>
+        <id>apache.releases</id>
+        <username>APACHE_USERNAME</username>
+        <directoryPermissions>775</directoryPermissions>
+        <filePermissions>644</filePermissions>
       </server>
     </servers>
   </settings>
 2. Ensure build/click.pom, build/click-extras.pom, build/click-mock.pom, build-nodeps.pom
has the correct dependencies and versions
 3. ant build-maven-bundles
-4. cd to directory maven-upload (this directory will be on the same level as the Click folder.
If Click is available at 'c:/dev/click', maven bundles will be under 'c:/dev/maven-upload')
-5. cd to each subdir in 'maven-upload' and execute the following command (Note: change <maven-artifact>.jar
to the actual filename):
-5.1. mvn deploy:deploy-file -DpomFile=pom.xml -Dfile=<maven-artifact>.jar -Durl=sftp://web.sourceforge.net/home/groups/c/cl/click/htdocs/maven2/
-DrepositoryId=sf.repo
+4. Digitally sign the maven bundles <maven-artifact>.jar. Note the -u argument is only
necessary if you have more 1 GPG Key.
+   gpg --armor [-u <GPG Key ID>] --output <maven-artifact>.jar.asc --detach-sig
<maven-artifact>.jar
+5. cd to directory maven-upload (this directory will be on the same level as the Click folder.
If Click is available at 'c:/dev/click', maven bundles will be under 'c:/dev/maven-upload')
+6. cd to each subdir in 'maven-upload' and execute the following command (Note: change <maven-artifact>.jar
to the actual filename):
+6.1. mvn deploy:deploy-file -DpomFile=pom.xml -Dfile=<maven-artifact>.jar -Durl=scp://people.apache.org:/www/people.apache.org/repo/m2-incubating-repository
-DrepositoryId=apache.releases



Mime
View raw message