Now that #155450: backport separate {cache_update_status} table and private non-volatile cache API from D6 core has landed, I'd like to ship a 5.x-2.4 ASAP. However, before I do, the following need to be done:

#431148: Make it easier to visually distinguish security updates on Updates report
#267724: Misleading instructions after enabling a module.
#235425: HEAD release always considered Not Supported during cron (this is a cvs_deploy issue, but I want to make sure the D5 backport works before tagging update_status).

Comments

dww’s picture

Status: Active » Needs review

Ok, all of those are now fixed. The end of the DRUPAL-5--2 branch hereby needs review. If you're using cvs_deploy, don't forget to update that to the end of DRUPAL-5, too, so you get the fix for #235425: HEAD release always considered Not Supported during cron.

andypost’s picture

Release need to point about visiting update.php (very big error message show on every page)

So now updates not fetched every time I visit admin/logs/update - tnx dww

dww’s picture

andypost: I'm trying to make sense of your comment. ;) I think you're just saying I should mention the need to visit update.php in the release notes (which I said I was planning to do). Otherwise, everything works great? ;) Thanks for testing!

andypost’s picture

Everything works great except big error message of non-existent table!

dww’s picture

Great. Well, there's nothing I can really do about that error message -- people need to run update.php after they upgrade.

dww’s picture

Status: Needs review » Postponed

Actually, there are a few update.module core issues that I'd like to consider backporting before shipping 5.x-2.4:

#445748: Add hook_update_projects_alter()
#243253: Update status module can cause white screen if the check for updates takes too long

I'd also like to consider:

#386636: Can't ignore unsupported projects

NancyDru’s picture

Hi, Derek. I'm having to update a high-volume site and wanted to get the most recent versions while I'm at it. Do you have any kind of a time line on this?

dww’s picture

I've been trying very hard for the past 2 weeks to deal with all the fallout and related issues. As you can see, almost every issue referenced in here is now fixed (in all versions of core -- no small feat!). The only pair of related issues that aren't yet committed are:

#445748: Add hook_update_projects_alter()
#162788: Include modules that aren't enabled

Probably I should just commit the hook invocation from #445748 and punt on the new feature from #162788... However, there's a slight problem with the #445748 backport that requires more thought (and code) before that's committable...

Anyway, my goal is still ASAP on this release...

NancyDru’s picture

Okay, for the moment then I will go with 2.3.

dww’s picture

@NancyDru: you could try 5.x-2.x-dev. It's pretty darn close to release. ;)

dww’s picture

Status: Postponed » Active

Ugh. Sorry for the delays, here. :( Life intervened...

Anyway, I think all the issues I care about for D5 update_status are now committed to DRUPAL-5--2 branch. If anyone is able to test 5.x-2.x-dev or the end of the DRUPAL-5--2 branch, I'd be very grateful. I've done some testing, but it's not exhaustive. But, I'd really like to tag and release 5.x-2.4 ASAP, as in this week. Real Soon Now(tm). ;)

Thanks!
-Derek

Dave Reid’s picture

I can do some testing on this shortly.

Dave Reid’s picture

Status: Active » Reviewed & tested by the community

Tested project ordering, disabled modules, and timestamps and it's all working great. Even hacked around .info files and played with really old datestamps in one sub-module and it picked up the latest datestamp value from the second sub-module. Messing with everything else worked as expected.

Let's release baby!

dww’s picture

Version: 5.x-2.x-dev » 5.x-2.4
Status: Reviewed & tested by the community » Fixed

OMG was this long overdue!

http://drupal.org/node/687088

Sorry,
-Derek

Status: Fixed » Closed (fixed)

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