Release update_status 5.x-2.4

dww - June 1, 2009 - 18:51
Project:Update Status
Version:5.x-2.x-dev
Component:Code
Category:task
Priority:critical
Assigned:dww
Status:reviewed & tested by the community
Description

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).

#1

dww - June 1, 2009 - 19:58
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.

#2

andypost - June 1, 2009 - 20:52

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

#3

dww - June 1, 2009 - 22:15

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!

#4

andypost - June 1, 2009 - 23:30

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

#5

dww - June 1, 2009 - 23:45

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

#6

dww - June 2, 2009 - 08:53
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

#7

NancyDru - June 12, 2009 - 19:00

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?

#8

dww - June 12, 2009 - 19:06

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...

#9

NancyDru - June 12, 2009 - 23:25

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

#10

dww - June 13, 2009 - 00:18

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

#11

dww - October 5, 2009 - 06:30
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

#12

Dave Reid - October 5, 2009 - 22:10

I can do some testing on this shortly.

#13

Dave Reid - October 10, 2009 - 04:43
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!

 
 

Drupal is a registered trademark of Dries Buytaert.