New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 721111 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Implement Chameleon Bundle Release Service

Project Member Reported by waihong@chromium.org, May 10 2017

Issue description

Joseph wrote the first plan for Chameleon Bundle Release Service.
https://docs.google.com/document/d/1VMTnV_h5v6T-nM9K3g3DA22K37RMHdbfn6_51RCwlHQ/edit?ts=57ced2f8#heading=h.5x3ixbhfn7em

The recent bundle release incident added much load to the lab people. Should implement this design asap to make the new deployment more smoothly.

Need some modification to the doc to reflect the points we discussed in the issue 718064.
 
It seems that I won't have bandwidth to implement this anytime soon. It would be nice if Moja could help on this project!
Labels: akeshet-pending-downgrade
ChromeOS Infra P1 Bugscrub.

P1 Bugs in this component should be important enough to get weekly status updates.

Is this already fixed?  -> Fixed
Is this no longer relevant? -> Archived or WontFix
Is this not a P1, based on go/chromeos-infra-bug-slo rubric? -> lower priority.
Is this a Feature Request rather than a bug? Type -> Feature
Is this missing important information or scope needed to decide how to proceed? -> Ask question on bug, possibly reassign.
Does this bug have the wrong owner? -> reassign.

Bugs that remain in this state next week will be downgraded to P2.
Labels: -akeshet-pending-downgrade Pri-2
ChromeOS Infra P1 Bugscrub.

Issue untouched in a week after previous message. Downgrading to P2.
Hi, this bug has not been updated recently. Please acknowledge the bug and provide status within two weeks (6/22/2018), or the bug will be archived. Thank you.
Status: Assigned (was: Available)

Sign in to add a comment