Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Tracking] Refactors prior to 1.x #660

Closed
1 of 5 tasks
crutchcorn opened this issue Mar 27, 2024 · 5 comments · Fixed by #812
Closed
1 of 5 tasks

[Tracking] Refactors prior to 1.x #660

crutchcorn opened this issue Mar 27, 2024 · 5 comments · Fixed by #812
Assignees

Comments

@crutchcorn
Copy link
Member

crutchcorn commented Mar 27, 2024

@crutchcorn crutchcorn self-assigned this Mar 27, 2024
@crutchcorn crutchcorn pinned this issue Jun 3, 2024
@austinm911
Copy link

austinm911 commented Jun 4, 2024

Will you include #476 as it breaks the ESLint/Biome rule ?

@crutchcorn
Copy link
Member Author

@austinm911 there's nothing to fix there. You can choose which API you want to use

@JackRobards
Copy link

Hey there! First off, this library is awesome 🔥 - thanks for all the hard work on it.

Is this ticket intended to be a sort of a Roadmap for important issues to fix before a 1.x release? I was looking around for a roadmap the other day and just found this issue.

It would be nice to know what you all are thinking as far as an initial release timeline - if you have any plans. The library feels close to release to me and already seems very usable. I'm considering using it on a project but would like to be sure I'm not misunderstanding the state of the library first 😁.

@crutchcorn
Copy link
Member Author

crutchcorn commented Jun 27, 2024

@JackRobards as far as I am aware, these denote the only breaking changes left before we 1.0. I'm 80% confident (and growing every day) that we will not have to make any further breaking changes until this occurs.

Once these are done, we will go from v0-beta (today) to v0-rc (stable, no breaking changes unless things go really wrong)

However, this doesn't mark the only things I want to do prior to 1.x. During RC (or maybe before) I'd like to address:

Once these issues are done, I think we're 1.x ready - pending integration with a production codebase.

As an aside; I know 1.x has taken a long time to get here. This is because I wanted to wait until we were extremely confident in what we're shipping. I'm very happy with how things are going today, but don't want to ship a v1, then a v2, then a v3 quickly. I want us to stay stable for some time in the future.

@crutchcorn
Copy link
Member Author

crutchcorn commented Jul 6, 2024

I'm happy to announce for anyone that's subscribed to this issue that we're officially in Release Candidate mode!

If you'd like to track our progress to 1.x, I've made an issue here: #813

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants