[
https://issues.apache.org/jira/browse/DERBY-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-4855:
---------------------------------
Attachment: derby-4855-07-aa-repackageDocsToSvnpubsub.diff
Attaching derby-4855-07-aa-repackageDocsToSvnpubsub.diff. This patch changes
our release build to account for the recent migration of the website to
svnpubsub.
This patch changes the repackagedocs target. Previously, that target created a
zip file of the user docs. In this zip file, the docs were rearranged into the
directory structure expected by our website. After running this target, the
release manager had to copy the zip file to people.apache.org and then unpack
it into the docs subdirectory of the rsynced website.
This process has been simplified significantly. Now the release manager does
the following:
o Runs "ant repackagedocs" as before. This now creates the re-arranged docs
subdirectory directly in the release manager's subversion website client.
o Uses "svn add" as necessary to put the newly created, release-specific docs
subdirectory under subversion control.
o Uses "svn commit" to commit the newly added docs subdirectory.
Touches the following file:
M build.xml
Committed to branches at the following subversion revisions:
1430417 - trunk
1430418 - 10.9
1430421 - 10.8
1430422 - 10.7
> Automate release publication steps
> ----------------------------------
>
> Key: DERBY-4855
> URL: https://issues.apache.org/jira/browse/DERBY-4855
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Reporter: Rick Hillegas
> Attachments: derby-4855-01-aa-docszip.diff,
> derby-4855-02-ab-releaseNotesTransformer.diff,
> derby-4855-03-aa-cgiTemplate.diff, derby-4855-04-aa-copyCgiScript.diff,
> derby-4855-05-aa-cliXconf.diff, derby-4855-06-aa-distributionLinks.diff,
> derby-4855-07-aa-repackageDocsToSvnpubsub.diff
>
>
> Right now, producing a Derby release involves 3 major chunks of work:
> 1) Producing the release notes (happens the week before the first release
> candidate is produced)
> 2) Producing release candidates (and submitting them to community vote)
> 3) Publishing the release distributions (after the community approves a
> candidate)
> This JIRA organizes work needed to automate the tasks which are part of step
> (3). Those steps are described here:
> http://wiki.apache.org/db-derby/ReleasePublication
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
