[drupal-docs] supplying version number for handbook pages

[Charlie Lowe]

Angie Byron wrote:
> Charlie Lowe wrote:
> 
> 
>>So in order to make sure that the version information can be provided as
>>easily as possible, i believe that tagging is going to be our best
>>solution.
>>
>>For tagging, how about: Drupal 4.6, Drupal 4.7, etc.
>>
>>Any suggestions?
> 
> 
> First, a couple questions and then hopefully some suggestions. :)
> 
> By "tagging" do you mean creating a taxonomy drop-down for book content where
> you can select a version number as you're creating/editing a page? Or is there
> some other mechanism I'm not aware of for tagging that exists?

That seems the easiest question.

> 
> Then my other question is, how do users continue to find "old" documentation?
> When I as an anonymous user go to node/######/revisions, I get an "Access
> Denied" error. Or will we have three handbooks, "Drupal 4.6," "Drupal 4.7," and
> "older stuff" (hope not, I could see all kinds of problems here)? Or will there
> be a block on the side that will provide links for people to switch between 4.7
> and 4.6 tagged documentation, if they exist?

The goal of the tagging is to provide users some information about 
whether the current page applies to the version they are working with, 
but does not provide a solution for maintaining separate handbook 
versions. We don't seem to have a good solution at this time to your 
questions about maintaining versions other than the fact that we can 
provide a copy of the current handbook for archival purposes using the 
printer-friendly feature, the docbook export function, and a pdf (when 
djun has the time).

Certainly, something better would be good if someone can come up with a 
solution and implement it. I would add that, IMHO, maintaining separate 
handbook versions--i.e., working on a current and legacy version at the 
same time--would seem highly impractical. The Drupal handbooks are 
growing at an incredible rate. I personally don't be believe that we 
have the resources to properly maintain a current, continually updated 
version, much less manage a solution which would require keeping more 
than one.