Skip to content

Bump version 2.58 to 3.0 #221

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.

Sign up for GitHub

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

Jump to bottom
Closed
Dovyski opened this issue Oct 18, 2014 · 2 comments
Closed

Bump version 2.58 to 3.0 #221

Dovyski opened this issue Oct 18, 2014 · 2 comments
Milestone
Flixel v3.0

Comments

@Dovyski
Copy link
Member

Dovyski commented Oct 18, 2014

When we released v2.56, it was ok to keep 2 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 with 2.5x will cause confusion and frustration for developers.
@Dovyski Dovyski added this to the Flixel v2.58 milestone Oct 18, 2014
@IQAndreas
Copy link
Member

This simple change will make it clear to any developer that things have changed significantly.

Excellent idea! I agree wholeheartedly.

@Dovyski
Copy link
Member Author

Dovyski commented Oct 21, 2014

Great! I will edit all milestones and our planning table.

@Dovyski Dovyski closed this as completed Dec 30, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
Flixel v3.0
Development

No branches or pull requests
2 participants
@IQAndreas @Dovyski