Relude has been "stable" (aka "unmaintained" 😂) for a couple years now, but it has been used in production without serious issue over that time. I think it's fair to say it's in a place where frequent breaking changes would be a bit unexpected.
In order to signal the expectation that things won't frequently break, I think it makes sense to release a version 1.0, and then start brainstorming and discussing larger changes we'd like to make to the project for a future 2.0 release.
Is there anything we'd like to do between now and 1.0? A few thoughts:
[ ] Get the "release" CI script working again, including doc publishing (#322 is starting to address this)
[ ] Identify and document which compiler versions (ReScript, Melange, BuckleScript) the 1.0 release is expected to be compatible with
[ ] Plan to release 1.0-compatible versions of relude-* libraries (parsing, dates, react helpers, etc)
Relude has been "stable" (aka "unmaintained" 😂) for a couple years now, but it has been used in production without serious issue over that time. I think it's fair to say it's in a place where frequent breaking changes would be a bit unexpected.
In order to signal the expectation that things won't frequently break, I think it makes sense to release a version 1.0, and then start brainstorming and discussing larger changes we'd like to make to the project for a future 2.0 release.
Is there anything we'd like to do between now and 1.0? A few thoughts:
relude-*libraries (parsing, dates, react helpers, etc)