[
https://issues.apache.org/jira/browse/DERBY-2227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468432
]
Jean T. Anderson commented on DERBY-2227:
-----------------------------------------
Yes; the built pages must be committed. Step 8 at
http://db.apache.org/derby/papers/derby_web.html suggests this:
svn commit --message "here is my commit message" src build/site
I usually put the commit info into a file called /tmp/changes.txt, then commit
like this:
svn commit --file /tmp/changes.txt src build/site
You must commit the built changes because the built site is checked out of svn
on people.apache.org. Step 9 then walks you through publishing the changes on
people.apache.org.
> Web Site - Add Checklist page for Doc updates for each release
> --------------------------------------------------------------
>
> Key: DERBY-2227
> URL: https://issues.apache.org/jira/browse/DERBY-2227
> Project: Derby
> Issue Type: Improvement
> Components: Web Site
> Reporter: Laura Stewart
> Assigned To: Laura Stewart
> Priority: Minor
> Attachments: Derby2227-1.diff, derby2227-1.zip, derby2227-2.diff,
> derby2227-2.zip, docscheck.html, site.xml
>
>
> Create a list of items to check and update for each release for the
> documentation.
> This list should include copywrite info, dates/time issues in the Working
> with Derby
> See this thread:
> http://www.nabble.com/Proposal---New-page-for-%22Release-Checklist-for-Docs%22-to-Derby-Doc-Web-Pages-%28WAS-Re%3A--jira--Commented%3A-%28DERBY-2194%29-A-few-more-problems-with-Working-with-Derby-manual-tf2947889.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
