From 0b679df09bb071adf27406b74d4c9faedd6c0ca4 Mon Sep 17 00:00:00 2001 From: glen_a_smith Date: Thu, 28 Jul 2011 05:11:05 +0000 Subject: [PATCH] More scratchy notes on the release cycle. --- doc/site/fml/index.fml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/site/fml/index.fml b/doc/site/fml/index.fml index 50ce9e9..4ba7159 100644 --- a/doc/site/fml/index.fml +++ b/doc/site/fml/index.fml @@ -222,7 +222,7 @@ List list = csv.parse(strat, yourReader);
  • As part of that process, you'll need to add your JIRA account name as a comment to our existing JIRA ticket.
  • Once you have access, change your Maven settings.xml on your local machine per Step 7a.1. in the Sonatype setup doc.
  • With all that in place, you can do a "mvn deploy" to release snapshots, or if you're ready to release, create a new branch, set the version in the POM, and "mvn release" again.
    • -
  • For prod releases, the release process puts things in the staging Nexus at Sonatype. It's a manual step from there to release (see step 8 of the Sonatype setup doc.
    • +
  • For prod releases, the release process puts things in the staging Nexus at Sonatype. It's a manual step from there to release (see step 8 of the Sonatype setup doc). First you have to "Close" the release in the staging repo (which checks the signatures and metadata), then they sent you an email, then you have to "Release" the release to central.
  • Finally, update the Sourceforge website with the latest Javadoc by using a "mvn site:deploy" (Details here)