Closed
Bug 1200478
Opened 9 years ago
Closed 9 years ago
Please deploy shavar 0.6.5 to STAGE
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Cloud Services
Operations: Deployment Requests - DEPRECATED
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: cloud-services-qa, Assigned: ckolos)
Details
------------------ RELEASE NOTES ------------------ https://github.com/mozilla-services/shavar/releases COMPARISONS https://github.com/mozilla-services/shavar/compare/0.6.4...0.6.4.1 https://github.com/mozilla-services/shavar/compare/0.6.4.1...0.6.4.2 https://github.com/mozilla-services/shavar/compare/0.6.4.2...0.6.5 TAGS https://github.com/mozilla-services/shavar/releases/tag/0.6.5 https://github.com/mozilla-services/shavar/commit/9d769577a2414d6c92f546cddcaf35eb0a563151
Updated•9 years ago
|
Assignee: nobody → ckolos
QA Contact: rpappalardo
Comment 1•9 years ago
|
||
I see there's was a new shavar-stage-72 deployed to STAGE this morning, but it looks like that was deployed prior to 0.6.5 being tagged. If 0.6.5 isn't currently staged, would you have time to spin one up tomorrow morning?
Flags: needinfo?(ckolos)
Assignee | ||
Comment 2•9 years ago
|
||
:rtilder is currently working on a bug that will end up bumping the release to 0.6.5.x. Until that's done, there's no reason to deploy 0.6.5 as the bug being worked is a go/no-go bug. The current stage version is 0.6.4.2; For *single* list functionality, it works. Key word, sadly, being "single".
Flags: needinfo?(ckolos)
Comment 3•9 years ago
|
||
:ckolos, OK, thought that might be the case. I'll close this out til we're ready.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•