1147124 - Update dialog has wrong "more information" link for point releases

Status: RESOLVED WORKSFORME

(SeaMonkey :: General, defect)

Description

[Mark]

I have SeaMonkey set to notify me when updates are available (not install automatically). Today it displayed a "Software Update" dialog notifying that SeaMonkey 2.33.1 is available.

The "View more information about this update" link goes to http://www.seamonkey-project.org/releases/seamonkey2.33.1/ which gives a 404 Page Not Found error.

I think the release notes for point releases are included on the main release. e.g. http://www.seamonkey-project.org/releases/seamonkey2.33/ says "These release notes describe ... for SeaMonkey 2.33 up to/including SeaMonkey 2.33.1".

I don't think it's just a case of the website not being updated yet, as I recall seeing this with previous point releases and the linked page never becomes available (e.g. for SeaMonkey 2.32.1, http://www.seamonkey-project.org/releases/seamonkey2.32.1 still gives a 404 Page Not Found).

Comment 1

[Rainer Bielefeld]

Seems to be fixed by an auto-forward to "http://www.seamonkey-project.org/releases/seamonkey2.33/"

@Reporter: Still reproducible for you?

Comment 2

[Mark]

http://www.seamonkey-project.org/releases/seamonkey2.33.1/ does now redirect to http://www.seamonkey-project.org/releases/seamonkey2.33/, and that redirect is followed when clicking the link in the "Software Update" dialog.

Has this been done as a one-off fix for this release, liable to occur again next time there's a point release, or has something been done to ensure similar redirects are set up in future?

Comment 3

[Philip Chee]

(In reply to Mark from comment #2)
> Has this been done as a one-off fix for this release, liable to occur again
> next time there's a point release, or has something been done to ensure
> similar redirects are set up in future?
CC Jens on this question

Comment 4

[Jens Hatlak (:InvisibleSmiley)]

(In reply to Mark from comment #2)
> Has this been done as a one-off fix for this release, liable to occur again
> next time there's a point release, or has something been done to ensure
> similar redirects are set up in future?

It can occur again whenever there's a point release and I forget to think of this special case.

The reasons why this happens are:
* point releases are always unscheduled
* redirects need to be added per individual point release, so cannot be done ahead of time (meaning before knowing that some major release is followed by a point release)
* there is no automation or automatic checks for website changes

In theory this could be prevented from happening again in the future by writing some check scripts that hook into my website changes preparation tools, or mitigate the chances by writing some guidelines, or have someone other than me check the staging website before the actual release. But either way a "fix" covering all future point releases would take time and effort beyond what I'm willing to do. I'll try to include the release notes redirect for future point releases from the start, though.

Comment 5

[Philip Chee]

Closing for this specific issue.