Comment 3 for bug 1487123

Galen Charlton (gmc) wrote :

I have a quibble with Remington's suggested follow-up: while I'm not opposed to the idea of not explicitly mentioning every version-upgrade script, I think it shouldn't stop short, lest somebody in a hurry wonders why things stop at 2.6.0. In other words, the last script mentioned should be the current version.

Automating that section is probably beyond what AsciiDoc attributes can do, but it wouldn't be hard to have build/tools/make_release generate a commit that handles it, removing a manual step from the release-building process.

Regarding a point that Josh made, I do think it would be very handy to continue to allow installers and upgraders to be able to copy/paste from plain text versions of the instructions contained in the tarballs. One way to do this might be to generate plain text output from the AsciiDoc, e.g., by doing something like this:

a2x -L -f text docs/installation/server_upgrade.adoc
cp docs/installation/server_upgrade.text UPGRADE

Note that I needed -L because server_upgrade.adoc contains section references to other parts of the manual; I also needed to install w3m.