Add planned dot releases

mozilla / releases_insights

Parse various sources (hg log, apis, crashes…) to get some insights on past releases such as uplifts per beta, top crash signatures per nightly…

Mozilla Public License 2.0

27 stars 8 forks source link

Add planned dot releases #32

Closed pascalchevrel closed 1 year ago

pascalchevrel commented 2 years ago

We are going to experiment having a planned dot release every cycle.

[x] Add planned dot release to the release view, GTB+release date
[x] Add planned dot release to the ics export, GTB+release date
[x] Add planned dot release to the past_release.php view, that means the last past release should behave differently in the template ~~- [ ] Ideally, we should probably support past releases in the Json API~~
[x] Should we announce the planned dot release on the home page?
[x] Add planned dot release to the /calendar view

DonalMe commented 2 years ago

@pascalchevrel could you modify the string displayed for the planned dot release? In the example of 103, 103.0.1 was not the planned dot release, but fx-trains lists 103.0.1 as the milestone. Note sure the best solution, maybe make the milestone version generic - possibly drop .0.{{ dot_release_count +1 }} from <th>Planned {{ release }}.0.{{ dot_release_count +1 }}</th>

pascalchevrel commented 2 years ago

@pascalchevrel could you modify the string displayed for the planned dot release? In the example of 103, 103.0.1 was not the planned dot release, but fx-trains lists 103.0.1 as the milestone. Note sure the best solution, maybe make the milestone version generic - possibly drop .0.{{ dot_release_count +1 }} from <th>Planned {{ release }}.0.{{ dot_release_count +1 }}</th>

I put a generic x: https://github.com/pascalchevrel/releases_insights/commit/cf2199c7ab919e7058366e000c1da402003efc83