Closed Bug 1390756 Opened 5 years ago Closed 5 years ago

improve docs and releasetasks release configs to ease the Fennec second graph submission

Categories

(Release Engineering :: Release Automation: Other, enhancement, P2)

enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mtabara, Assigned: mtabara)

References

Details

(Whiteboard: [releaseduty])

Fennec ships in two graphs the same way Firefox does[1], for major releases. But the docs for Fennec and the release-configs[2] never made it.

Time to add both so that future releases are copy-paste procedure and not just hacking on bm85.

[1]: https://github.com/mozilla/releasewarrior/blob/master/how-tos/relpro.md#how-1
[2]: https://github.com/mozilla-releng/releasetasks/tree/master/releasetasks/release_configs
During 55.0 release last week, after I munged the graph and resubmitted only what was necessary as the second graph for Fennec, I forgot `git checkout .` the changes on bm85 and that spooked folks this week. Bad Mihai.

Will fix this properly with docs + release configs so that next time we have some docs to offer us guidance.
Is this is just the Fennec X.0 releases, so we have three graphs for Fennec then ? And two otherwise (releasetasks + nightly decision task).
(In reply to Nick Thomas [:nthomas] from comment #2)
> Is this is just the Fennec X.0 releases, so we have three graphs for Fennec
> then ? And two otherwise (releasetasks + nightly decision task).

To be fully honest, in case of Fennec, I consider graph2 only the Fennec X.0 release graph from second week.
Otherwise, graph2 is the same with candidates_fennec graphid and I just look-it up that way.

We could improve releasewarrior as well to do that as graph3 and make these things clear/consistent across all types of releases.

What do you think?
Whiteboard: [releaseduty][ready] → [releaseduty]
Depends on: 1347635
Work for this bug is tracked already under bug 1347635 so we can close this as duplicate.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.