Closed Bug 685159 Opened 13 years ago Closed 12 years ago

Put in place a plan for keeping production build and release configurations regularly up to date

Categories

(Mozilla Messaging Graveyard :: Release Engineering, defect)

Product:
Mozilla Messaging Graveyard
Component:
Release Engineering
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: standard8, Unassigned)

References

Details

(Keywords: meta, Whiteboard: [ETA ?]) 

We keep falling significantly behind on buildbot updates, and missing the goodness that MoCo is creating.

We need to find a way to get on top of the latest updates and to keep them moving forward.
Depends on: 609337
Depends on: 633968
Depends on: 682078
No longer depends on: 633968
I suggest we set aside a predetermined day each week to a) pull and test the latest changes to buildbotcustom and b) close the tree (if needed) and roll those changes out.  What is rolled out could be the previous week's merge so we have 1 week of soak time on staging before upgrading.

Adding more automated tests to buildbotcustom should be considered as well, to reduce the manual testing burden.
Updating bug title - the work will be done elsewhere so let's just discuss the process here.
Summary: Update production buildbot build and release configurations to latest and put in place a plan for keeping regularly up to date → Put in place a plan for keeping production build and release configurations regularly up to date
Once we're integrated with Firefox build infrastructure, we'll get this for free.  See bug 698843.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.