403194 - Bump nightly mapping to get Firefox Trunk updates going again

Status: RESOLVED FIXED

(AUS Graveyard :: Administration, task)

Description

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

Attachment: Match on 3.0* instead of 3.0a*

The Firefox trunk version was bumped to 3.0b2pre yesterday, which doesn't match any of the mappings in the AUS config for nightly updates, so no updates for those nightly testers today.

This patch gives us some breathing room. No doubt we'll have to revisit this when it's clear what's happening with branching near/after Fx3.

Comment 1

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

Little known 11th commandment: thou shalt not meddle with other people's bugs.

(the work for this bug is not in the trivially simple patch, but in the acceptance tests and getting it live, none of which I am able to do)

Comment 2

[Reed Loden [:reed]]

(In reply to comment #1)
> (the work for this bug is not in the trivially simple patch, but in the
> acceptance tests and getting it live, none of which I am able to do)

The acceptance tests are in CVS under webtools/aus/tests/. You should be able to run them yourself, afaik. There's even a README (*woo* for documentation)!

Getting something pushed live has never (in my opinion) required setting the assignee to the person doing the actual pushing. Lately, AMO developers have been using a "push-needed" keyword to note things to get pushed live and doing the push in a separate bug from the actual patch. This allows for the actual bug with the patch to remain assigned to the user who wrote the patch, which makes much more sense (again, in my opinion).

Comment 3

[Michael Morgan [:morgamic]]

Let's not get completely lost in minutiae.

Thx Nick -- this passes acceptance tests and yes, is a simple patch, but it's good practice to get another set of eyes on it regardless.

Checked in on trunk.  It's tagged for prod and staging and I filed bug 403225 for the push.

Comment 4

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

Thanks for the quick turnaround Mike.

Comment 5

[Reed Loden [:reed]]

(In reply to comment #3)
> Checked in on trunk.  It's tagged for prod and staging and I filed bug 403225
> for the push.

Could that bug be made not-confidential? I wouldn't think a push bug would have any private/secret information in it, and it only hurts the community who want to know what's going on with AUS by having it confidential.

Comment 6

[Michael Morgan [:morgamic]]

(In reply to comment #5)
> Could that bug be made not-confidential?
Yea, it could but I don't have permissions to do that.