If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Please deploy shavar 0.6.5 to STAGE

RESOLVED WONTFIX

Status

Cloud Services
Operations: Deployment Requests
RESOLVED WONTFIX
2 years ago
2 years ago

People

(Reporter: Cloud Services QA, Assigned: ckolos)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
------------------
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
Assignee: nobody → ckolos
QA Contact: rpappalardo
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

2 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)
:ckolos, OK, thought that might be the case. I'll close this out til we're ready.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.