Milestone bar: show next major, not maintenance, release

[sadielbartholomew]

Currently the website milestone bar displaying progress towards the next release shows 7.8.5, which would be the next maintenance one:

however this is not appropriate for various reasons:

• Cylc 8.0.0 is now the most significant release to anticipate, & where progress towards it is useful to show;
• Cylc 7.8.5 as a far-down-the-line maintenance release should not get many PRs against it, & indeed it currently only has a single closed one, such small numbers making the progress figure look extreme (e.g. it currently looks like we are now ready to release 7.8.5!);
• Cylc 7.8.4 is hoped, & perhaps expected, to be the last 7.8.x release, so 7.8.5 may not even become an actual release.

So we should change the release with progress displayed by milestone bar to be Cylc 8.0.0 via the cylc-8.0.0 milestone, or if the alpha releases mean that the progress towards calculated from, & in terms of, GitHub PRs is not representative, we could formulate some logic e.g. totalling alpha release figures, to give a better indication.

[kinow]

I think there was some discussion around this before, though I can't recall what was the decision. Maybe the idea is to show the next stable/production-ready release, and 7.8.5 would still be closer than 8.0.0? Though I don't have any strong opinion here.

Also, I think to change the next release, that's done in the milestones tab in cylc-flow. I think the JS code in this website is simply picking the one with the earliest release date.

[matthewrmshin]

For now, the easiest thing to do is to simply move back the expected date of the cylc-flow 7.8.5 milestone. 😈 The team can then decide on whether to continue to feed the milestone of cylc-flow, or move to feed something else.

[hjoliver]

Once we branched off 7.8.x my intention was to highlight 7.8.x releases on the web site Download button, because that's still the recommended "production" version of Cylc.

Recent changes to the release data retrieval (by @matthewrmshin I think) are a big improvement, but it's still a bit confusing as displayed (given our 7.8.x and 8.0ax overlapping releases...) as @sadielbartholomew has highlighted.

For the moment I'll push the 7.8.5 date back beyond 8.0a2 ...

[hjoliver]

... decide on whether to continue to feed the milestone of cylc-flow, or move to feed something else.

Yeah I had been thinking cylc-conda, but discussion on Riot last night suggests we won't need that after publication to conda-forge :grimacing: ... so, TBD...