Comments for Coop

Comment on My add-ons by Barbara J Cooper

Barbara J Cooper — Fri, 28 May 2010 20:51:14 +0000

Not much of use to me – I wish all this neat stuff existed back when I was a programmer.

I do use AdBlock Plus and Greasemonkey, and Personas. I really like a Greasemonkey app called FFixer which makes FaceBook a lot less cumbersome.

Comment on My add-ons by Coop

Coop — Fri, 28 May 2010 19:32:12 +0000

@Walt: that’s a pretty big one to forget, isn’t it?

I *do* have it installed, but it’s disabled most of the time.

Comment on My add-ons by Walt

Walt — Thu, 27 May 2010 02:10:11 +0000

Firebug. Don’t forget Firebug.

Comment on ThinnerBox by Coop » My add-ons

Coop » My add-ons — Wed, 26 May 2010 19:35:23 +0000

[...] – I use a few simple Greasemonkey scripts to tame the output from some of the web tools I look at frequently for [...]

Comment on One Point Five by Coop » My add-ons

Coop » My add-ons — Wed, 26 May 2010 19:35:04 +0000

[...] realized the other day that I hadn’t done a post about my favorite add-ons since Firefox 1.5. The add-on landscape has changed a lot since that time, sufficiently so that I think it merits an [...]

Comment on Reclaiming space on stage.mozilla.org by Coop

Coop — Tue, 25 May 2010 21:23:57 +0000

We hashed out a revised plan on the newsgroups:

http://groups.google.com/group/mozilla.dev.planning/msg/3ec37a1f5275d502?

It boils down to the following:

1) Keep all releases for all products online and available. There’s no need to remove them.

2) Keep all en-US nightly builds for all products online and available. There’s no need to remove them.

3) Delete nightly artifacts for all products that are not useful inregression hunting. Specifically, this means deleting installer files (linux and windows) and xpis from 2009 and earlier. This could represent a one-time space recovery of almost 900GB. Individual products can opt out of this cleanup with sufficient cause.

4) Automate the deletion of nightly MAR files older than one month. Only the most recent MAR files are required. This would be done across all products. (unchanged)

5) Delete builds from older candidates directories after official release. This will reclaim up to 13G per build attempt per release. This will be a manual process. (unchanged)

6) Automate the removal of nightly artifacts older than 6 months for all products that are not useful in regression hunting.

Comment on Reclaiming space on stage.mozilla.org by James Napolitano

James Napolitano — Sun, 23 May 2010 12:44:53 +0000

Maybe instead of deleting all nightly builds that are older than a certain date, you could delete all but one build per time period. E.g. leave one build per week or one per month. This would still enable binary searches to a decent degree of precision.

Comment on Reclaiming space on stage.mozilla.org by Standard8

Standard8 — Thu, 13 May 2010 08:41:39 +0000

You failed to mention Thunderbird, was that included in the list of other products?

In any case, yes we’d like to help clean up too, but it’ll be about a week before we start discussion on it (due to 3.1 rc1 pressures).

Comment on Reclaiming space on stage.mozilla.org by Samuel Sidler

Samuel Sidler — Thu, 13 May 2010 03:27:42 +0000

As recently as six months ago, I had to go back to builds in 2005 to track down a regression on a security bug. I’d cite the bug, but I can no longer see them. I know others have had to track down regression ranges even further back in the last year. I’d prefer archiving to deleting.

I’d also be opposed to deleting (as opposed to archiving) candidate builds because I know QA has often needed to reference them when verifying bugs in later releases.

Comment on On 1-on-1s by - John O'Duinn's Soapbox

- John O'Duinn's Soapbox — Mon, 26 Apr 2010 17:31:00 +0000

[...] Coop, in his own polite understated way, told me we were going to try this format. It worked great for Coop’s 1×1 with Armen, and he thought it might improve Coop’s 1×1 with me. Our first meeting took longer then [...]