forked from AdamAtomic/flixel
-
Notifications
You must be signed in to change notification settings - Fork 17
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
Bump version 2.58 to 3.0 #221
Milestone
Comments
Excellent idea! I agree wholeheartedly. |
Great! I will edit all milestones and our planning table. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When we released
v2.56
, it was ok to keep2
as the major version number, since the API was identical to the previous one. A handful of bugfixes were made, but things remained retro-compatible.That's not the case with
v2.58
anymore. As our feature planning table shows, several changes have been made to the API: classes were moved, method signatures were changed, new (complex) features were added, etc.I think we should bump Flixel Community version to
3.0
. This simple change will make it clear to any developer that things have changed significantly. Sticking with2.5x
will cause confusion and frustration for developers.The text was updated successfully, but these errors were encountered: