287143 - parse release-checklist.html and feed version-specific data into new files for each app/branch combination

Status: RESOLVED INVALID

(www.mozilla.org :: General, defect)

Description

[Chase Phillips]

release-checklist.html contains data which is specific to the current versions
of the apps.  Over time, this data changes, resulting in changes to the
release-checklist.html page.  However, when we need to revisit a release/branch,
we may end up using the newer data on the older code (where it may be invalid or
incomplete).

If we designed a system that better shared the workload of process and
app/version-specific data, we could let the app/version-specific data ride along
with the code as it is branched/tagged.

For example, instead of including a list of files that include the year that
need to be bumped, include a pointer to the app file in the correct LXR with a
header note such as:

  Bump the year in the following files for
    * Mozilla 1.7.x (links to http://lxr.mozilla.org/mozilla1.7/source/foo/bar)
    * Aviary 1.0.x (links to http://lxr.mozilla.org/aviary101branch/source/foo)
    * Trunk
        * Firefox (links to ...)
        * Thunderbird (&c)

The same technique could be used to track and include references to the
application version numbers, what extra directories and files should be checked
out to make a release tag, &c.

Comment 1

[David Boswell]

Reed and Sam, is this something we can mark as invalid or move to another component?  I assume that any release checklist information today is kept on MDC or the wiki and not on www.mozilla.org.

Comment 2

[Reed Loden [:reed]]

I've never heard of this before... INVALID sounds fine.

Comment 3

[Samuel Sidler (old account; do not CC)]

Yeah, this was from forever ago and we don't use it anymore.