I spent time on the documentation in three ways:
1. Updating the links from 0.95 to 1.0 and from 0.94 to 0.95. This can
be avoided if we call the directories 'latest' and 'previous'.
2. Updating the compliance page. I did this with emacs regexes, but
they are tricky. I think the setup of the page
Hi Vincent,
I was actually thinking of converting only the product docs, not the
website. For just HTML output, I find Forrest quite nice, but the
linking for the various versions creates a lot of overhead for a release.
And that's basically what triggered that thought.
Basically, I'd suggest to
Hi,
Jeremias Maerki wrote:
> On 05.07.2010 17:13:32 Simon Pepping wrote:
>> In compliance, I kept only 0.95, 1.0 and trunk. This caused extensive
>> changes to comments.
>
> I guess keeping track of various versions on the website is one of the
> biggest issues why doing FOP releases is so hard.
