chore: add release plan [skip ci] #4853
Conversation
manniL
requested review from
a team,
aldarund,
alexchopin,
Atinux,
clarkdo,
galvez,
kevinmarrec and
pi0
Codecov Report
@@ Coverage Diff @@
## dev #4853 +/- ##
=======================================
Coverage 91.19% 91.19%
=======================================
Files 73 73
Lines 2361 2361
Branches 582 582
=======================================
Hits 2153 2153
Misses 190 190
Partials 18 18Continue to review full report at Codecov.
|
|
Having the possibility to skip one major release while you cannot guarantee there is a minimum amount of time between major releases is not really helpful. People/businesses need time to upgrade so saying its supported until 2 weeks after some arbitrary major release cycle doesn't say anything and doesnt mitigate the risk of using outdated software. If you plan to release a major version every 6 months and support major versions until the second major release after, then just say that each major is supported for at least one year. This could mean more work for us (in the unlikely case there is more than one major release in a half year), but in the end its much more clear for people/businesses what they can expect. |
|
@pimlie Very good point here. Will change that |
|
Probably you already planned this, but it would be nice to have a page like this that lists all eol's: https://wiki.ubuntu.com/Releases Even nicer would be to include the eol in the distribution packages and automatically print a warning e.g. 1 month before the eol date that they should check for an update (as in new minor release with an extended eol date) or upgrade (to a new major). |
|
Yes, a release overview page is planned (with EOLs, etc.) Regarding the warning: That's a nice idea! Feel free to raise an issue or submit a PR if you have an implementation in mind |
Resolves nuxt/rfcs#9
To the rendered view