HOWTO RELEASE COCOON 3: Preparations
------------------------------------

* check your workstation's settings as described at http://cocoon.apache.org/1199_1_1.html (step 1)

* update src/main/changes/changes.xml and src/main/site/apt/download.apt in the 'parent' module
* set all versions in the generated pom.xml files of all archetypes
  . cocoon-archetype-sample/src/main/resources/archetype-resources/pom.xml
    sync with cocoon-samples/pom.xml
    update to the to-be-released version of Cocoon
  . cocoon-archetype-parent/src/main/resources/archetype-resources/pom.xml
    sync with parent/pom.xml
    update to the to-be-released version of Cocoon
  . cocoon-archetype-block/src/main/resources/archetype-resources/pom.xml
    update dependency versions (see parent/pom.xml)
    update to the to-be-released version of Cocoon
 
* mvn release:prepare release:perform -P archetypes
  (to be invoked from the root directory of Cocoon 3 trunk)
 
* tag all modules manually (see svn-release-tags.bat or svn-release-tags.sh in the root directory of Cocoon 3 trunk)
* set all versions in the genreated pom.xml files of all archetypes back to SNAPSHOT
* update <parent> sections of unreleased modules (cocoon-sample-webapp)

HOWTO RELEASE COCOON 3: After a successful vote
-----------------------------------------------

* move the distribution files cocoon-all-[version]-dist.tar.gz. cocoon-all-[version]-dist.tar.gz.asc
  cocoon-all-[version]-dist.zip, cocoon-all-[version]-dist.zip.asc from
  from /x1/www/people.apache.org/builds/cocoon/org/apache/cocoon/all/cocoon-all/[version] 
  to /x1/www/www.apache.org/dist/cocoon/3.0/ (people.apache.org)

* remove old distribution artifacts from /x1/www/www.apache.org/dist/cocoon/3.0/ 
   (--> they are still available at http://archive.apache.org/dist/ where they will never be deleted)

* copy the Maven artifacts to the Apache sync repository (people.apache.org):
  cp -R /x1/www/people.apache.org/builds/cocoon/ /x1/www/people.apache.org/repo/m2-ibiblio-rsync-repository/

* update the 3.0 branch of our site in SVN

  It's a manual process. There is an ASF requirement that all site content has to be managed by SvnPubSub
  Apache Cocoon reuses the old site (simplified) deploy procedure.

  Checkout this URL.

    svn co https://svn.apache.org/repos/asf/cocoon/site/site/ [site]

  And run

    mvn -P reports site-deploy -Ddocs.deploymentBaseUrl=file://[path-to-site]

  from the 'parent' module base directory creates the site.

  Then commit the newly generated content. SvnPubSub will take care on pushing the new content online in a short while.

* send an announcement mail to announce@apache.org, users@cocoon.apache.org, dev@cocoon.apache.org
  . make sure to always refer to 'Apache Cocoon' ('Cocoon' is not sufficient).
 
HOWTO TEST A COCOON 3 RELEASE
-----------------------------

* use the new artifacts in projects that depend on previous or SNAPSHOT versions. Add the Cocoon staging repository profile to your ~/.m2/settings.xml

<?xml version="1.0" encoding="UTF-8"?>
<settings xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
  <profiles>
    <profile>
      <id>cocoon-staging</id>
      <repositories>
        <repository>
          <id>cocoon.staging</id>
          <name>Cocoon staging repository</name>
          <url>http://people.apache.org/builds/cocoon</url>
        </repository>
      </repositories>
      <pluginRepositories>
        <pluginRepository>
          <id>cocoon.staging</id>
          <name>Cocoon staging repository</name>
          <url>http://people.apache.org/builds/cocoon</url>
        </pluginRepository>
      </pluginRepositories>
    </profile>
  </profiles>
</settings>

and use it: e.g. mvn install -P cocoon-staging

* use all archetypes:
mvn org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-7:create -DarchetypeGroupId=org.apache.cocoon.archetype-sample -DarchetypeArtifactId=cocoon-archetype-sample -DarchetypeVersion=[version] -DgroupId=com.mycompany -DartifactId=mysample -DremoteRepositories=http://people.apache.org/builds/cocoon/ 

mvn org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-7:create -DarchetypeGroupId=org.apache.cocoon.archetype-block -DarchetypeArtifactId=cocoon-archetype-block -DarchetypeVersion=[version] -DgroupId=com.mycompany -DartifactId=mysite -DremoteRepositories=http://people.apache.org/builds/cocoon/ 

mvn org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-7:create -DarchetypeGroupId=org.apache.cocoon.archetype-parent -DarchetypeArtifactId=cocoon-archetype-parent -DarchetypeVersion=[version] -DgroupId=com.mycompany -DartifactId=myparent -DremoteRepositories=http://people.apache.org/builds/cocoon/ 

mvn org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-7:create -DarchetypeGroupId=org.apache.cocoon.archetype-webapp -DarchetypeArtifactId=cocoon-archetype-webapp -DarchetypeVersion=[version] -DgroupId=com.mycompany -DartifactId=mywebapp -DremoteRepositories=http://people.apache.org/builds/cocoon/ 

* check GPG, MD5 and SHA1 files