You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currenly releasing 3.x.y releases, and we're still backporting fixes to 2.x.y and 1.x.y. 2.0.0 has been released in October 2021, and I'm not sure whether anyone is still using 1.x.y. (I haven't seen any bug reports for it.)
What do you think about declaring stable-1 End of Life and stop updating it (and removing it from the weekly CI)? If you don't think it should be done soon, when do you think it's time for it?
ISSUE TYPE
Admin
COMPONENT NAME
collection
The text was updated successfully, but these errors were encountered:
As a general policy: how about 'supporting' only the latest two branches (i.e. main and the latest stable-x) and making all other stable branches EOL? That would mean that stable-2 would become EOL once stable-3 is created and 4.0.0 released, etc.
SUMMARY
We are currenly releasing 3.x.y releases, and we're still backporting fixes to 2.x.y and 1.x.y. 2.0.0 has been released in October 2021, and I'm not sure whether anyone is still using 1.x.y. (I haven't seen any bug reports for it.)
What do you think about declaring stable-1 End of Life and stop updating it (and removing it from the weekly CI)? If you don't think it should be done soon, when do you think it's time for it?
ISSUE TYPE
COMPONENT NAME
collection
The text was updated successfully, but these errors were encountered: