I would only keep the manual for the minor version. A patch release
should not introduce any significant changes for a particular branch,
yet the manual is likely to have a large number of unrelated changes
coming from newer minor releases. As such it's mostly confusing.
I would also only keep the manuals for the supported versions and,
maybe, 1.6.0.
My $0.02,
Hadrian
On 03/12/2012 09:53 AM, Daniel Kulp wrote:
We now have the svn "space" setup for the website and I'm going to start
populating it with the content. You'll likely see some rather big commits
shortly to do that. However, I have a couple questions related to "old
content":
1) The manual/ dir currently has a bunch of manuals all the way back to
camel 1.2:
camel-manual-1.2.0.pdf camel-manual-1.6.0.pdf camel-manual-2.0.0.pdf
camel-manual-2.5.0.pdf camel-manual-2.8.4.pdf camel-manual-1.3.0.pdf
camel-manual-1.6.1.pdf camel-manual-2.2.0.pdf camel-manual-2.6.0.pdf
camel-manual-2.9.0.pdf camel-manual-1.4.0.pdf camel-manual-1.6.3.pdf
camel-manual-2.3.0.pdf camel-manual-2.7.0.pdf camel-manual-2.9.1.pdf
camel-manual-1.5.0.pdf camel-manual-1.6.4.pdf camel-manual-2.4.0.pdf
camel-manual-2.8.0.pdf
Do we really want to keep all of them around on the site? That totals 90MB
of space. I'm thinking just the 2.8.x+ that we "support", but maybe even
back a little longer.
2) Likewise for /maven:
camel-2.2.0 camel-2.4.0 camel-2.6.0 camel-2.8.0
camel-2.3.0 camel-2.5.0 camel-2.7.0 camel-2.9.0
These total 1GB of space.
3) Old (deleted) pages: we have 57 html pages on the site right now that
have been deleted from Confluence (or renamed). The old sync process
didn't remove the HTML pages so we have all these old .html pages still
"live" on the site (although likely not linked to). I assume we should
just remove these and not carry them over.
I'm mostly interested in what to do about
--
Hadrian Zbarcea
Principal Software Architect
Talend, Inc
http://coders.talend.com/
http://camelbot.blogspot.com/
