You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 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)The text was updated successfully, but these errors were encountered: