We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I think v4 has been in development for long enough now. We should push back any major changes to v5 and just release it already.
This is a tracking issue for planning the release.
The text was updated successfully, but these errors were encountered:
I'm proposing the following schedule:
7th June 2024 — Fork the insp4 branch and set it as the default. Then, release v4.0.0rc1.
14th June 2024 — Release another release candidate if any more bugs have been reported.
21st June 2024 — Release another release candidate if any more bugs have been reported.
28th June 2024 — Release v3.17.1.
29th June 2024 — Release v4.0.0 final.
We can probably speed up the release schedule a bit if only a few bugs get reported.
UPDATE: Pushed back to not collide with my schedule so much.
Sorry, something went wrong.
No branches or pull requests
I think v4 has been in development for long enough now. We should push back any major changes to v5 and just release it already.
This is a tracking issue for planning the release.
The text was updated successfully, but these errors were encountered: