There's been a few issues that need review piling up and potentially more changes coming soon down the pipe. Our own implementation of Funnelback is heavily patched in a way that I consider unsustainable in the long run, if we wanted to add new features or fix new bugs, which we do.
I'd like to propose that we put out a 2.0.0-beta3 release containing new features before we put out any new major versions or RCs. I'm happy to handle this process but only with the blessing of the other maintainers.
There's a few blanks in this issue description but I'll keep filling them in as I go.
Some good candidates for a possible 2.0.0-beta3 include, in terms of maintenance, bug fixing and developer quality of life:
There are also candidates for features that SLNSW have been using in PROD since we patched Funnelback. These might not be ideal to merge into a beta3 until we've developed tests for them.
Finally, I'd like to get Funnelback 16 support ✨ Funnelback 16 support Active into a future release.
TODO determine changes based on issues above.
TODO determine changes based on issues above.
TODO determine changes based on issues above. There will be at least one config-related change.
Active
2.0
Miscellaneous
Go for it
I favor a release early/release often workflow and often do releases for each commit
Thanks Lee! Given you prefer frequent releases, I might look at doing a 2.0.0-beta3 for the issues that are already committed to 2.x, and do additional ones for individual features as you suggested. The CI/CD one would be a good one to get in so we can start testing all changes yet to come.