db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "DerbySnapshotOrRelease" by RichardHillegas
Date Wed, 19 May 2010 13:02:08 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The "DerbySnapshotOrRelease" page has been changed by RichardHillegas.
http://wiki.apache.org/db-derby/DerbySnapshotOrRelease?action=diff&rev1=151&rev2=152

--------------------------------------------------

      * Be sure to specify that the src.tar.gz requires gnu tar to unravel (because of our
usage of ant tar to create this, using longfile=gnu for handling long filenames).
      * Use search-and-replace to change all occurences of the old version number to the new
one.
      * Replace the old release notes section with the appropriate fragment from `RELEASE_NOTES.html`
in the new release.
-     * Remove all square brackets [] from the release notes page. When the cgi machinery
sees square brackets, it truncates the release page. (Should be handled by the ReleaseNote
vetter?) In addition, remove all of the blockquote tags; Forrest swallows everything bracketed
by blockquotes. In addition, remove the table of contents (the table of links to anchors in
the release notes); Forrest generates its own table of contents, which is sufficient; if you
leave the original table in the release notes, Forrest will transform it into a list of dead
links.
+     * Remove all square brackets [] from the release notes page. When the cgi machinery
sees square brackets, it truncates the release page. (Should be handled by the ReleaseNote
vetter?) In addition, remove all of the blockquote tags; Forrest swallows everything bracketed
by blockquotes. In addition, remove the table of contents (the table of links to anchors in
the release notes); Forrest generates its own table of contents, which is sufficient; if you
leave the original table in the release notes, Forrest will transform it into a list of dead
links. Also remove the mini table of contents in the Issues section. Forrest will munge it
for the same reason.
      * The boilerplate at the beginning of the release page contains a link to verification
instructions at the end of the page. Make sure that you include the verification boilerplate
at the end so that the link works.
+     * Remove all internal links from the release notes (links to anchors inside the page
itself). Forrest removes your anchors and insists on creating its own anchors using an id
generator.
  
    a. In order for the release HTML file to be pulled into the build, it is necessary to
add a line to the <uris> section of `src/documentation/conf/cli.xconf`. Near line 310
of that file, add: `<uri type="append" src="releases/release-x.y.z.w.html"/>` (with
the correct version for your release).
  

Mime
View raw message