Repository navigation
Shifting priorities across v1, v2, and v3
#1559
meatballhat
started this conversation in
General
Replies: 2 comments 5 replies
|
v1. Yes freeze the release to v1.22.10 and say that no bug fixes, features will be supported. Delete the v1 branch altogether ? Not sure about that. Maybe give people 6 months advance warning before doing it ? v2. Freeze features. Bug fixes only. v3. I'm still not seeing a reason why someone would want to upgrade to v3. Right now it has no features that are not present in v2. There needs to able atleast one MAJOR feature in v3 which everyone is asking for prior to even releasing an alpha tag. |
5 replies
⬆️ These are done ✅
⬆️ These are done ✅
⬆️ These are done ✅ |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
This discussion is primarily meant to make space for conversation about shifting development efforts to focus on
v3. The details of what I have in mind would include:v2series as support mode onlymainbranch asv2-maintbranch, which is intended to be long-livedv2.23.x1 will be the last minor release in thev2seriesv2series will only receive bug fixes and security fixes, meaning patch releases tov2.23.xonlyv3series as alphav3-dev-mainasmainbranchv3series so that projects may begin experimenting with features that are not available inv2v2-mainttomainmergev3-dev-maintomainand use themainbranch for allv3workv1series as unmaintained / unsupportedv1.22.10will be the last release in thev1seriesdelete thev1branch (whoops! meant to do that a while ago!)v1branchv1-unsupportedPlease contribute your thoughts in this discussion, especially if you see anything in these details that conflicts with your ability to keep using this library. Thank you! 💖
Footnotes
at the time of this writing,
v2.23.0was the current minor version, but more minor versions in the v2 series may arrive in the meantime, which I think is fine ↩All reactions