Closed (works as designed)
Project:
Drupal core
Version:
6.16
Component:
update.module
Priority:
Normal
Category:
Support request
Assigned:
Reporter:
Created:
1 Mar 2010 at 00:45 UTC
Updated:
23 Mar 2010 at 09:01 UTC
I had the 3.0 version installed from back in December 31, 2009. I noticed a lot of commits stated in various issues (I monitor the issue queue through my email), but no new version of HS, not even a dev release. Let me say here that I didn't check the module's page in the meantime, I simply relied only on my site's 'Available updates' page. I thought there must have been some reason delaying a new dev release. So, I waited.
Call me a newbie if this is not the case, but I thought that versions were checked against their 'Last updated' date. It seems not to. In the HS releases' page the status is as follows:
6.x-3.0: listed on top, date: December 31, 2009 - 15:42, Last updated: December 31, 2009 - 15:45
5.x-3.0: next in list, date: December 31, 2009 - 15:30, Last updated: December 31, 2009 - 15:35
6.x-3.x-dev: next, date: December 1, 2008 - 05:24, Last updated: March 1, 2010 - 03:07
So, my guess is that the initial commit date of the first dev version is checked and not the 'Last updated' one. This makes the latest 6.x-3.x-dev versions appear to be older than the last stable release and not being mentioned as an update at all. If you never install the latest stable and wait for the next dev (thus always keeping dev releases installed), the issue doesn't occur. Once you install the latest stable, you aren't offered newer dev releases.
It is either that or it beats me(?)
Steps to reproduce (4 cases):
- install 3.0 stable
- check your site's 'Available updates' page for new versions. No dev build mentioned as newer release.
- install any dev build older than 3.0 stable's release date. (I happen to have a December 23, 2009 laying around).
- check your site's 'Available updates' page for new versions. Both the 3.0 stable and latest new dev build are shown as updates.
- install any dev build newer than 3.0 stable's release date, but not the latest one. (I have downloaded Feb 23, 2010 before Mar 01, 2010 was released).
- check your site's 'Available updates' page for new versions. Both the 3.0 stable and latest new dev build are shown as updates.
- install the latest dev build that is newer than 3.0 stable's release date
- check your site's 'Available updates' page for new versions. Only the 3.0 stable release is shown as an update (as expected).
I have a lot of modules installed and haven't noticed this kind of behavior with them. Also, I don't know if this is an Update Status core Drupal module's bug/known issue/by-design or if something needs to be changed in the way dev releases are being built/committed.
Comments
Comment #1
michelleIf you are running a stable version of any module, it doesn't suggest a dev version to you. You only get dev version suggestions if you're running a dev. That's normal behavior.
Michelle
Comment #2
wim leersI bet this is just the Drupal Update Status system lagging behind. It doesn't promises real-time updates. It just promises it'll warn you soon. That is, as soon as its various caching layers have been updated.
I bet it'll show up correctly by tomorrow :)
However, for me it's already showing up:
That's from admin/reports/updates on a live site of mine. As you can see, it's also lagging behind, since the last snapshot is actually March 1 already. Cron has just run, so that's not it. So the only thing left to conclude that it's indeed the drupal.org Update Status infrastructure that is causing the delay, most likely due to caching.
Comment #3
klonosEither that or as Michelle said in #1 it is Drupal Update Status by-design behavior and I need to check for latest dev releases manually (visit modules' pages) once I happen to install a stable.
As a 'workaround' you could be making sure in the future that once you've committed/built a new stable, you also build a new dev based on that stable. This way, people helping with dev testing will get the latest ;)
... and it seems I am a complete newbie :P
Thanks Michelle & Wim for taking the time to answer.
Comment #5
wim leersYep, Michelle's definitely right. My bad.
dev releases are not really encouraged to be installed, hence they don't show up in Update Status when not really necessary.
You can track updates to dev snapshots by subscribing to the RSS feed at http://drupal.org/project/cvs/172915. Every time there's a commit there, the dev snapshot will be updated within 4 hours. Not perfect, but it works :)
Comment #6
klonosI know (now)... I've played with my other installed modules a bit and found out that it is so.
My workaround is to simply not upgrade to stable versions if I want to have latest devs ;)
Thanx everyone.
Comment #7
wim leersHeh :)
You're welcome!
Comment #9
klonosactually this should be marked 'by design', as per #1
Also it is drupal core update issue and not HS specific.
Comment #10
dwwagreed this is "by design", and calling it a support request -- there's no task here that needs/needed to be done. thanks, michelle, for pointing out the design. ;)
Comment #11
klonos@dww: Yeah... the task thing was because the issue started from the HS project originally. In #9 I've made the appropriate changes but missed this one. Good catch! ...but since I have some real-life use cases that need a workaround to this, I am about to change it to a feature request...
Comment #12
klonosCreated a new issue for my suggestion... #750352: Provide an option to also offer dev builds as updates if they are newer - for advanced users & beta testers