I need some explanation here. Why is the development version recommended instead of the official version?
see screenshots

Comments

dww’s picture

Project: Drupal core » Drupal.org infrastructure
Version: 6.1 »
Component: update.module » Packaging
Assigned: Unassigned » dww
Category: support » bug

The problem is in the .xml files generated on drupal.org that the Update status module is using, not in the client code in Drupal core. In this particular case, the DB fields for the views 6.x-2.x-dev release were slightly invalid compared to what the script generating the .xml files was expecting. That resulted in the -dev release being listed first in the .xml file, which confused the Update status client code. I fixed the DB record, and re-ran the script to generate the .xml files, so if you "fetch manually" again on your available updates report, you should see the right thing.

However, I checked and there are about 40 other -dev releases with similarly wrong DB info. Instead of fixing all of those manually, I'm just going to work on a patch to the script that generates the .xml files to be more robust in this case, and ensure that the -dev releases are always listed where they're supposed to.

dww’s picture

Status: Active » Needs review
StatusFileSize
new2.87 KB
dww’s picture

Project: Drupal.org infrastructure » Project
Version: » 5.x-1.x-dev
Component: Packaging » Releases

The patch is relative to project/release/project-release-create-history.php, so I'm moving this issue to a more appropriate queue. I did test this on p.d.o and it works as intended, but if anyone else wants to give it a quick look before I commit and deploy, that'd be nice.

aclight’s picture

Code looks good but I'm not sure how best to test this.

dww’s picture

Status: Needs review » Fixed

I know it works since I ran it on d.o. Committed to HEAD and DRUPAL-5. Deployed on d.o.

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.