What Never To Do: The Case of Foolish Foo
After extensive upgrades to the code from 5.x-1.x (CVS branch DRUPAL-5), the developers decided they ought to set 5.x-2.x (DRUPAL-5--2) to the recommended branch. Presumably, this would increase their testing base. Unfortunately, they had only made 5.x-2.0-alpha2 (DRUPAL-5--2-0-ALPHA) release.
The next day, hundreds of Drupalites around the world woke up, and checked their highly profitable production Drupal websites. Being conscientious users, they had been checking their module updates regularly, so they saw Update Status dancing on fire, telling them:
Upgrade Foolish Foo to 5.x-2.0-alpha now!
Actually the update.module remains quite silent as it never force you to upgrade to a new major version until the version you are using is still marked as supported. The result in the update status is: "Also available: 5.x-2.0-alpha". It force you to upgrade only if you remove the supported flag from the 1.x branch..
I would like to see a new page about update status, which dww should review, because there are many misunderstandings (and unclear parts) in the module functionality...
Comments
Comment #1
arianek commentedweeding through ancient issues...... what exactly are you looking for for new content? there is info about the update status module on its module page here http://drupal.org/handbook/modules/update do we just need a link?
Comment #2
pasqualleno. I would like to see a documentation without errors and correct examples, explaining every possible scenario.
Comment #3
arianek commentedagain, can you be more specific about what you are requesting as far as corrections and new documentation?
also are there mistakes you see on the http://drupal.org/handbook/modules/update page or http://drupal.org/node/197584 that you can provide corrections for?
Comment #4
leehunter commentedClosing this issue, since a year has passed without enough information to take action.