Or maybe let that "previous versions" link take the user to a completely separate archive page that has a big note in bold saying that issues should not be filed against this documentation.

Keeping previous versions outside the forrest build path would have the advantage of not bogging down forrest builds.

Now, it has to be pointed out that 10.0 is not a previous version. :-)

It's probably too late to separate out 10.1 from 10.0 in the dita source, but moving forward we should version the dita doc source like the derby code does.

In the meantime a simple measure that would make it clear that the dita docs contain 10.1 features would be to change the doc path from derby/docs to derby/docs/10.1, for example, this:

   http://incubator.apache.org/derby/docs/getstart

to this:

   http://incubator.apache.org/derby/docs/10.1/getstart

 -jean


Jeff Levitt wrote:
Here's an idea to help distinguish those docs from the
current builds.

The current manuals page (when it includes the
original docs) looks like this:

-About
-DITA
-Original manuals

...or something to that effect, with each item
expandable.  What if we changed the name of that
bottom item to "Previous versions" and added one more
nested nav item within it for 10.0?  So you'd have:

-About
-DITA
+Previous versions
   -Version 10.0

Expanding the Version 10.0 twistee would of course
bring up the originally contributed docs.  Right now
it might not make a lot of sense since we only have
one previous version, but in time, when we fill that
"Previous versions" heading with more releases, it
makes for better organization, and I think it is less
likely to confuse the new user.

--- "Jean T. Anderson" <[EMAIL PROTECTED]> wrote:

I removed links to the old manuals in a change
committed in revision 168509. Undoing this action is as easy as restoring
the previous site.xml file.


 -jean

Jean T. Anderson wrote:

As the note on

http://incubator.apache.org/derby/manuals/index.html


says, corrections are only being made to the DITA

docs. The original


docs will not be updated.

I realize that the formats for the new docs might

not be "perfect", but


perhaps it's time to at least remove the visible

links to them so people


see the most current info by default.

Unless I hear opposition, I'll remove web site

links to the original


manuals. They'll still be there (and also in svn);

the web site just


won't provide navigation to them.

thoughts?

-jean





Reply via email to