[drupal-docs] supplying version number for handbook pages

[Bèr Kessels]

without getting into technical details, i think the SVN/CVS way is the way to 
go.
* on a release  4.7 we branch the handbook, page by page. Everytime a page is 
ready for 4.7 it is branced and tagged.
* HEAD pages are sort-of drafts, They are either very up to date and describe 
stuff in current Drupal HEAd, or are so old they never got updated to 4.7
* A release branch is stable. Changes can be made if there are obvious errors. 
otherwise one should work on HEAD. 

I know. There is no code to achieve this. This is just what i think would 
solve all below-mentioned issues.

I think this could be achieved with a small module that uses revisions + an 
extra database table to track branches. I do not volunteer to write this :)

Ber


Op zaterdag 05 november 2005 16:09, schreef 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.
 Bèr
-- 
 [ Bèr Kessels | Drupal services www.webschuur.com ]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://drupal3.drupal.org/pipermail/documentation/attachments/20051105/b238718b/attachment.pgp