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
Just a general question, how do we organize versions for releases?
Current code and setup in 'next' branch will be v4 or v5?
Looking at v4 (#5) todo list, looks like most of it no longer relevant as we started to use Gulp setup from latest Kickoff version.
I guess we need to set up a new 'update plan' for the next release of Statix
The text was updated successfully, but these errors were encountered:
Yeh, you’re exactly right. I’ll take a look at that list and see what’s still relevant now that we’ve moved onto gulp.
The next major release will be tagged at v4 – don’t think we’re far away from being able to release now after your update.
Sorry, something went wrong.
Have updated the release plan in #5 – closing this issue as anything relating to the new release should be kept there.
No branches or pull requests
Just a general question, how do we organize versions for releases?
Current code and setup in 'next' branch will be v4 or v5?
Looking at v4 (#5) todo list, looks like most of it no longer relevant as we started to use Gulp setup from latest Kickoff version.
I guess we need to set up a new 'update plan' for the next release of Statix
The text was updated successfully, but these errors were encountered: