Open vursen opened 1 year ago
Thanks for using Vaadin! We appreciate your help and we’ll take care of this as soon as possible.
This information is maintained on the https://vaadin.com/roadmap page, at the end in the "Support" section. I don't think we should duplicate it here.
This information is maintained on the https://vaadin.com/roadmap page, at the end in the "Support" section.
The problem is that it's well hidden and hard to discover, as I mentioned internally last year:
UPD: the GitHub org page has a link to the Roadmap, but https://vaadin.com does not.
This information is maintained on the https://vaadin.com/roadmap page, at the end in the "Support" section. I don't think we should duplicate it here.
Right, I guess I need to clarify it a bit. The pain point is minor versions. The roadmap rather gives you the general principle of how you figure out which and for how long minor versions are maintained. You still have to calculate their start and end of life yourself and this is what you do over and over unless you have written it down somewhere. This is why I believe it makes sense to put them on paper. We could list minors in the roadmap, don't have to be in the platform readme indeed.
Describe your motivation
When fixing a bug or implementing a feature, it always takes extra time to find out which versions the bug or the feature should be backported to. It would be helpful to have a table with the currently maintained versions and their support period somewhere in the platform readme.
Here is an example of how it might look like:
https://github.com/nodejs/Release
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response