I got prompted to update the update module from 5.x-1.2 to 5.x-2.0 beta. But on my production site I don't want to test/use beta modules. So it would be nice to be notified only if new stable versions are available (or being able to set a switch to get that kind of behavior). Then again, I'm quite new to Drupal, and one project's beta is another project's stable, so maybe it's ok to use beta, as opposed to DEV versions, on Drupal production sites?

Comments

dww’s picture

dww
we/he/they
commented
Assigned: Unassigned » dww
Category: feature » support
Status: Active » Fixed

a) that was the old version of the software (5.x-1.2) warning you to upgrade, not the currently supported verision.

b) the primary reason it did so is that the co-maintainers of this project have dropped support for the 5.x-1.* series, since it has a bunch of fundamental limitations that have been fixed in the new version. if you go to http://drupal.org/project/update_status you'll see that the 5.x-2.0-beta release is the only one immediately visible for download. it's now the recommended version, so that's what update_status recommends that you upgrade to. since the 6.x core code freeze is so soon, and we're planning to move this into core, we're putting all of our energy into the 5.x-2.* version. and yes, we're probably 2 of the most responsible maintainers you'll find in all of contrib, so our betas are usually higher quality than you might otherwise expect. ;) that said, there have already been some fixes to the beta, and yet more enhancements, so a 5.x-2.0-beta2 should be out soon.

cheers,
-derek

Eudaimonius’s picture

Eudaimonius commented
Version: 5.x-2.0-beta » 5.x-1.2

So the update module will always point to the latest version recommended by the module maintainers, and if they recommend using a "beta" version, it should be ok to install it, so a "beta switch off" isn't needed. Thanks for the explanation and the nice work on the update module :)

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)