956777 - Replace Firefox release notes supporting "buglist" pages with links to bugzilla searches

Status: RESOLVED DUPLICATE of bug 1041712

(www.mozilla.org :: Legacy PHP system, defect)

Description

[Steven Garrity [:sgarrity]]

A subset of Firefox release notes have an associated buglist.html file, linked from the release notes page, listing bugs fixed in that release.

As the release notes are being migrated to a database-driven system over in Bug 948114, we should address these files too.

Newer release notes seem link link to a bugzilla search, which we can probably do for these older versions as well.

We'll have to run through each buglist.html file, see if there is a consistent element to perform a bugzilla search on, and replace the link with the bugzilla search link. If there isn't consistent metadata on which to search in the bugs, we'll have to mass edit the bugs to add something searchable.

I'm not sure if we should bother creating redirects from the old buglist.html files to the new bugzilla search URLs. Thoughts?

http://www.mozilla.com/en-US/firefox/10.0/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/10.0.1/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/11.0/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/12.0/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/13.0/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/14.0.1/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/15.0/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/15.0.1/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/16.0/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/16.0.1/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/16.0.2/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/17.0/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/17.0.1/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/18.0/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/18.0.1/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/18.0.2/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/19.0/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/20.0/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/4.0b10/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/4.0b11/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/4.0b12/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/4.0b8/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/4.0b9/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/4.0rc1/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/5.0/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/5.0.1/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/5.0beta/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/6.0/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/6.0beta/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/7.0/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/7.0beta/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/8.0/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/8.0beta/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/9.0/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/9.0.1/releasenotes/buglist.html
http://www.mozilla.com/en-US/firefox/9.0beta/releasenotes/buglist.html
http://www.mozilla.com/en-US/mobile/14.0.2/releasenotes/buglist.html

Comment 1

[Justin Crawford [:hoosteeno] [:jcrawford]]

A cursory glance suggests that it may not be easy to find a common attribute. For example, this page...

http://www.mozilla.org/en-US/firefox/10.0/releasenotes/buglist.html

...links to these two bugs...

https://bugzilla.mozilla.org/show_bug.cgi?id=688158
https://bugzilla.mozilla.org/show_bug.cgi?id=704612

...and I can't see that they share anything unique to this release. I'll be happy to learn otherwise.

These documents can easily be parsed to grab the bug IDs [0]. Unfortunately, each one contains so many bugs that the search/mass edit URL is too long for BMO's webserver to handle [1]. In other words, we can't just use the bug IDs to create an arbitrary list via URL, and for the same reason we can't do a normal mass bug edit using that URL. 

We could break the URL into more manageable chunks and mass edit the chunks. The script linked below might seed that effort.

We should probably talk with some folks in Engineering before doing so, since this will send tens or hundreds of thousands of bugmails. 

Alternatively, we could see if anyone who works on BMO would like to run arbitrary SQL to add a few whiteboard tags for us...

[0] https://gist.github.com/hoosteeno/8291004
[1] https://docs.google.com/spreadsheet/ccc?key=0Algxlsc2cLlldHRiU0p4MjZQUDFrSWI1WGxaZEV4S3c&usp=sharing

Comment 2

[Justin Crawford [:hoosteeno] [:jcrawford]]

Attachment: Links to bug lists for these releases

Steven, does the attached file look like it'll work to solve this bug? It contains HTML forms for each of those URLs that take you to a complete bug list. These forms could replace the current link. Code for this is here:

https://gist.github.com/hoosteeno/8324004

Thanks to Kohei for the tip.

Comment 3

[Kohei Yoshino [:kohei]]

yay!

Comment 4

[Steven Garrity [:sgarrity]]

(In reply to Justin Crawford [:hoosteeno] from comment #2)
> Steven, does the attached file look like it'll work to solve this bug?

The form submission has the drawback of not being a link you can copy/paste, etc. Since these are just legacy release notes, though, I think this will do fine.

This does mean that we can't redirect to the buglist from the URLs we'd be removing. We could redirect those buglist urls the associated release notes page that contains this button.

Comment 5

[Josh Mize [:jgmize]]

I'm +1 on just redirecting the buglist URLs to the release notes pages-- I believe we should be able to do that redirect with a single regex instead of needing an individual redirect for each page.

Comment 6

[Jennifer Bertsch [:jbertsch]]

(In reply to Josh Mize [:jgmize] from comment #5)
> I'm +1 on just redirecting the buglist URLs to the release notes pages-- I
> believe we should be able to do that redirect with a single regex instead of
> needing an individual redirect for each page.

+1

Comment 7

[Steven Garrity [:sgarrity]]

I've run through each remaining buglist.html file in SVN and the corresponding Bedrock-powered Release Notes page for each already contains the button/link to the list of bugs directly in Bugzilla.

So, we can redirect all /*/X.X.X/releasenotes/buglist.html to the corresponding Release Notes page.

However, we will have to wait until the /b/ bedrock redirect is turned on for all release notes, or at least all versions with a buglist.html file.

Of the releases with a buglist.html file, the only two that don't have a bedrock-powered release notes page ready are http://www.mozilla.org/b/en-US/firefox/18.0.2/releasenotes/ and http://www.mozilla.org/b/en-US/firefox/18.0.2/releasenotes/

I'm adding Bug 939984 as a blocker. Once those release notes are in, we can add redirects for these buglist pages and remove the files from SVN.

Comment 8

[Steven Garrity [:sgarrity]]

It turns out some of these releases were just falling back to a default bug search link, but I have now updated all of releases in nucleus that have a corresponding buglist.html file in SVN.

We are still waiting on all release notes as per comment #7.

Comment 9

[Steven Garrity [:sgarrity]]

All of these buglist.html files are being archived as part of Bug 1041712.