Closed Bug 650424 Opened 14 years ago Closed 14 years ago

schedule time to make changes to dirty profiles

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: anodelman, Assigned: lsblakk)

References

Details

There are two requested changes to the dirty profiles used during talos testing. I need to know when would be a safe time to roll these out. As these change the profiles themselves there is a higher possibility of causing number wobble in the dirty tests.
Blocks: 649123, 600980
Assignee: nobody → lsblakk
I'll take this and help make this happen next week. With warning, I would guess we can do it at the end of PST working day?
After further discussion in IRC with Alice, this doesn't need releng shepherding. Alice can notify dev.planning and dev.platform so that they are away of potential shaking in the numbers as talos adjusts to new profile info. Those emails also reach Releng so we'll know what's coming too. Resolving.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
oh also, ftr, this is because of two things: alice has cruncher access and can update the profiles, and we don't do that many downtimes right now so waiting for one (or scheduling one) is not that useful when this can be done in the background as long as there is appropriate notice.
A NPOB change is highly encouraged for developers after the talos bundle gets deployed. anode when you email the mailing lists you can ask for someone to propose a NPOB patch to push after the talos bundle gets refreshed.
I do not know what an NPOD patch is. Also, this isn't a talos bundle change.
(In reply to comment #4) > A NPOB change is highly encouraged for developers after the talos bundle gets > deployed. I don't even know what this is - please don't use acronyms without saying the whole definition at least once Also this bug is WONTFIX'd after my conversation with alice in IRC - if you need to get more information to the ATeam in general I believe we have wikis for that.
Not Part Of The Build generally is shortened to NPOTB. aka Not Part of the Default Build NPOTDB.
I've added: https://wiki.mozilla.org/Auto-tools/staging#Dirty_Profile_Changes_or_other_NPOB to get the word out on this fabulous acronym :)
If a change is going to affect talos number besides announcing it ahead of time I am encouraging to try to look for something to check-in to mozilla-central. This makes it easier to notice for developers and the regression detection email. Otherwise, the regression email would point to the next change to land unto the tree and developers could backout that change by mistake. I will add a note to the page.
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.