Closed
Bug 1397908
Opened 7 years ago
Closed 7 years ago
[releasewarrior] Add upcoming changes to releasewarrior ahead of beta to identify potential issues
Categories
(Release Engineering :: Release Automation: Other, enhancement, P3)
Release Engineering
Release Automation: Other
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: kmoir, Assigned: kmoir)
References
Details
(Whiteboard: [releaseduty])
No description provided.
Assignee | ||
Comment 1•7 years ago
|
||
Add add a new section in releasewarrior to support this
Summary: [releasewarrior]Add upcoming changes to releasewarrior ahead of beta to identify potential issues → [releasewarrior] Add upcoming changes to releasewarrior ahead of beta to identify potential issues
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → kmoir
Updated•7 years ago
|
Priority: -- → P3
Comment 2•7 years ago
|
||
I think we can close this, now that we have a much more robust staging enviroment with a better cadence. We'll be able to catch some of the issues easier. What do you think Kim?
Flags: needinfo?(kmoir)
Assignee | ||
Comment 3•7 years ago
|
||
Yes, sounds good. I think all the releaseduty folks are familiar with adding possible issues to release warrior ahead of time.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(kmoir)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•