- πΊπ¦Ukraine pazhyn Kharkiv
Maintainers are not willing to work on making 1.0 stable.
2.x is in active development instead.
Closing as outdated to clean up the issue queue. - π³πΏNew Zealand xurizaemon Εtepoti, Aotearoa π
@pazhyn, is it worth re-opening this issue to co-ordinate 2.x if that's where development is happening? Or create a new issue to do same?
Release coordination issues β can be really useful to coordinate between maintainers, contributors and consumers. If that works for you, it can help redirect contributions towards the upcoming branch, and clarify for existing users where things are at with 1.x vs 2.x.
I don't see an existing 2.x coordination issue, and if it's a total rewrite as suggested in #3239062: 'Stable Release Request' Issue Template β then the information here may be outdated and a fresh issue might make more sense
- π¬π§United Kingdom nicrodgers Monmouthshire, UK
@pahzyn wrote:
Maintainers are not willing to work on making 1.0 stable.
2.x is in active development instead.@pahzyn is there an issue where this is stated or discussed? I've had a quick look through the issue queue and can't see any mention of it. Thanks.
- πΊπ¦Ukraine Matroskeen πΊπ¦ Ukraine, Lutsk
Sorry, there was no clear plan for
2.0.xversion. The alpha version is already available for testing and your review.
See: https://www.drupal.org/project/rabbit_hole/releases/2.0.0-alpha1 βIf you have some feedback about 2.0.x, you can use this task: π± Rabbit Hole 2.0 testing (upgrade, config, usage) Active .
Thanks!