181262 - Add XML or RDF file that contains the latest current build

Status: RESOLVED WONTFIX

(Release Engineering :: General, enhancement)

Description

[Henrik Gemal]

To be able to determain if your Mozilla is up-to-date it would be really nice if
you were able to query a xml file at mozilla.org to check the latets current
build version. Tinderbox or perhaps the build tool could update this XML file
when the files are moved to ftp.mozilla.org

The xml file would contain info about the useragent string and the build data
and the platform.

Comment 1

[Henrik Gemal]

the xml should of cause be public available that's the hole point. Something like:
http://mozilla.org/versions.xml
or
http://versions.mozilla.org/trunk.xml
http://versions.mozilla.org/release.xml

Comment 2

[timeless]

xml? rss? rdf?

i'd say this is more of its own webtool since it probably needs to hook up to
stage instead of tinderbox.

Comment 3

[Henrik Gemal]

How does the "Update Notification" works?
Edit -> Prefs -> Advanced -> Software Installation

it seem that the update notification service isn't hooked up yet, but that also
need a file:
chrome://communicator-region/locale/region.properties

Comment 4

[Henrik Gemal]

some "region.properties" points to:
http://home.netscape.com/updates/updates.rdf
but that's a 404

btw here is the spec:
http://www.mozilla.org/xpapps/updates/spec.html

Comment 5

[Christian :Biesinger (don't email me, ping me on IRC)]

>it seem that the update notification service isn't hooked up yet

Beonex uses it, probably also Netscape 7.

Comment 6

[Henrik Gemal]

Netscape 7 points to http://home.netscape.com/updates/updates.rdf which is a 404...

Comment 7

[Henrik Gemal]

now http://wp.netscape.com/updates/updates.rdf works.

cant mozilla have an updates.rdf too?

Comment 8

[Brian 'netdragon' Bober]

Is this bug still relevant? A lot has changed in the last year.

Comment 9

[Gervase Markham [:gerv]]

Well, the basic idea is still relevant - it would be good to have a single
central machine-queryable mechanism of determining the current release versions
of Mozilla products (e.g. the start page could use it).

Gerv

Comment 10

[Worcester12345]

bump

Comment 11

[cls]

Not exactly sure where this belongs under mozilla.org but it's not a tinderbox bug as it morphed to involve the status of released products, not development trees.

Comment 12

[Nick Thomas [:nthomas] (UTC+12)]

This was originally filed when the in-app update system was poor, but it works really well now. Both nightlies and releases can just do "Help > Check for updates"