56180 - Broken mozilla.org links

Status: VERIFIED FIXED

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

Description

[Gervase Markham [:gerv]]

[Following a discussion in the newsgroups about Netscape-only web links on 
mozilla.org]

[ This bug belongs to [e-mail], who does not have a Bugzilla 
account]

The page at the URL given contain links to Netscape-only internal resources. 
Please could you make the documents at the end of these links available to the 
rest of the world by checking them in to the mozilla.org CVS tree and updating 
the links as appropriate? 

http://www.mozilla.org/quality/browser/front-end/testplans/browser-bookmarks.htm
l
http://www.mozilla.org/quality/browser/front-end/testplans/browser-history.html
http://www.mozilla.org/quality/browser/front-end/testplans/browser-toolbars.html

If you do not have time to do this, feel free to mail me the document and I will 
ensure that this gets done.

Gerv

Comment 1

[Dawn Endico]

[e-mail] is [e-mail].
Reassinging to him.

Comment 2

[lchiang]

The "broken links" are references to the UI documents which the UI group had not 
placed on mozilla.org at the time the test plans were written. They don't hinder 
in running the tests outlined in the plans and I've mentioned this to asa.

At that time (more than a year ago), we had a choice: not publish any of QA test 
plans for Mozilla to view/use or publish the QA test plans as is so that at 
least the test plans would be functional for Mozilla to use. We had no control 
over the UI group to publish their specs and wanted to get as much of our test 
plans out to Mozilla as possible.

Once Seamonkey RTM is complete, then Netscape QA can follow up with the UI group 
to see if they have updated their UI specs to mozilla.org and update our test 
plans accordingly. If you don't want our tests to be on mozilla.org because they 
reference broken links, let me know and I will remove all of our test plans 
until we have time to focus on updating them.

I'd suggest that you may want to contact the UI group as to their plans for 
publishing the UI specs. Thanks.

Comment 3

[Claudius Gayle]

accepting bug. I'll wait for a decision from on high or traction from UI.

for my 2 cents removing the links(all of mine are marked with a '#') cripple netscape internal
folks. I'm not going to fork the testplans and put them up internally because 1) that creates
an uncessary divide internal vs. external and 2) I'm sooo not going to maintain two sets,
especially w/o CVS internally.</.02>

Comment 4

[Claudius Gayle]

accepting. I have to go dig up current, published UI specs for these areas

Comment 5

[Gervase Markham [:gerv]]

If they need digging up, are they either "current" or "published"? :-)

Gerv

Comment 6

[James Cox]

accepting QA for mozilla developer docs.

some of these bugs have been around for a _long_ time. Reporters, would you
please review the bugs, see if the issues have been resolved, and close bugs
appropriately.

I will do a full review of all bugs not touched in one week (8th April). 

Thanks.

</spam>

Comment 7

[Anne (:annevk)]

Attachment: patch #1

This fixes the links on all files.

Comment 8

[Anne (:annevk)]

Nicolas, could you check this in as well?

(Are there more people doing checkins? I got a lot of patches waiting to be
checked in. I will try to mail that form for a CVS account today...)

Comment 9

[Anne (:annevk)]

Done.