[drupal-docs] Tag handbook pages with major versions

[puregin]

On 7 Sep 2005, at 7:37 PM, Charlie Lowe wrote:

> Version tagging is a great idea. But before we jump into this,  
> there are a few things we ought to talk about:
>

This begs the question, 'how will tagging be used?'

   Do we want to be able to select a Drupal version and see the  
handbook corresponding to our selection?

   How will book structure and taxonomy interact?

   How will 'missing' content be handled?  For example, if there is  
no content for 'administering blocks' tagged for 4.6, do we display a  
blank page?  Give a warning and fall back to an earlier version?  How  
will book navigation work?

   Or perhaps we just want to be able to display all tags associated  
with the page.

   I guess all of this is to say - I'm a bit uneasy that we're  
grasping at tagging to try to impose some external structure on  
documentation which is in parts fundamentally lacking in cohesion  
(pardon me for saying so).

As far as versioning goes, I think it's a great idea.  But versioning  
by tagging seems to be the wrong approach.  How would we handle  
branches?  What about content that is independent of version?

     Djun