- Issue created by @Mars0test
- π¦π·Argentina abelpzl
There are still issues blocking the release of a stable version.
I don't think a stable release is possible without first finishing the tasks detailed in " Stable release roadmap β ". - π«π·France Mars0test
Honestly, I didnβt know there was a roadmap, but when I check the issues, Iβm a bit disappointed because, from my point of view, thereβs nothing significant enough to block a first stable version.
You have a great MVP that works without patches unless specific needs arise.
These kinds of things are just nice features that existed in D7, but with the breaking changes, itβs not uncommon for modules to lack certain features after migration.
Forcing consumers to compromise on stability is worse than that.I would also add that, in terms of feature releases, I prefer smaller iterations over a big-bang approach.
- π³π±Netherlands pahles
First, is there ever going to be a stable release for 2.0.0, since there already is a 3.0.0-alpha1?
I agree with mars0test, there are no real blockers for a first stable release. The two alpha release blockers were last updated 3 years ago, the question is, are they still valid? A number of stable release blockers where last updated 2-3 years ago too.
I think creating a stable release (preferably compatible with Drupal 11) would make sense and then a new roadmap to address the other issues.
- π¨π¦Canada joseph.olstad
rc11 tagged release has been available, I haven't heard of many complaints so I may tag 2.0.0 after D11 support is reported as a success with rc12 or rc14