Before HEAD opens up and the API changes all over the place, we need to branch the docs in contrib.

I post this to infrastructure rather than do it myself because I tried to do it for the 4.7 release and somehow totally messed it up last time. :P

So if someone would be so kind as to take care of this and copy and paste what they typed in to do it for future reference, that would be awesome. :D

Comments

moshe weitzman’s picture

i would prefer if we waited until the first API change before branching. In my experience, folks most diligently edit HEAD and not a branch. if we open now, i fear we will miss a few useful edits on DRUPAL-5

drumm’s picture

I'll want to do this before making 5.x and 6.x versions available on api.drupal.org.

As moshe mentioned, no APIs have changed; I'm not in a rush to do this quite yet.

webchick’s picture

Hmmm...

Just as long as people remember to do this before the first API change in 6.x... It's quite confusing now for newbies (we're teaching a course this week to people brand new to Drupal) having to look in "HEAD" for 5.x documentation, but have to tell them "but, pretty soon this will actually be called 5.0 docs, so only use HEAD until you see 5.0 in the list" :P

webchick’s picture

Had another report of this here: http://drupal.org/node/113266

With chx's menu patch in, HEAD is already diverging from 5.x in a big way. Can we please get the docs branched?

pwolanin’s picture

While I could branch the developers docs, the bigger problem (e.g. the menu system) is that the API site itself apparently has not been reconfigured to look for the DRUPAL-5 branch.

I thought I saw discussion on the devel list of a mojor upgrade to the APi module, and that that's what we're waiting for?!?

dww’s picture

Status: Active » Fixed

drumm did this.

Anonymous’s picture

Status: Fixed » Closed (fixed)

Component: CVS » Other