As mentioned in https://github.com/fastify/fastify/issues/229#issuecomment-358108181, it would be a good idea to have a published LTS strategy. Even if it is as simple as "we only support the active X release of semantic version X.Y.Z releases."
Use this issue to hash it out.
jsumners
All 4 comments
I would like to call 1.0.0 LTS (supported) for a 6 month timeline minimum. And maintenance (security fixes) for another 6 months.
All semver-major work should happen in master but we would issue backport PRs to a 1.x.x branch.
And we need semver-* tags.
I would also note that we should start squashing commits when landing, because that would simplify backporting.
mcollina
on 17 Jan 2018
I can get onboard with all of those suggestions.
jsumners
on 17 Jan 2018
@fastify/fastify do you agree with the proposal set for by @mcollina?
jsumners
on 18 Jan 2018
Absolutely :)
nwoltman
on 18 Jan 2018
Related issues
zhaoyao91
路
3Comments
zairl23
路
3Comments
lfurzewaddock
路
3Comments
allevo
路
3Comments
bhanuc
路
4Comments
Most helpful comment
I would like to call 1.0.0 LTS (supported) for a 6 month timeline minimum. And maintenance (security fixes) for another 6 months.
All semver-major work should happen in master but we would issue backport PRs to a 1.x.x branch.
And we need semver-* tags.
I would also note that we should start squashing commits when landing, because that would simplify backporting.