Just a heads-up, we are planning on going 1.0 next weekend. This release will not have any significant new features, but indicate a general maturity that we think we’ve arrived at. With the arrival of our Gradle based project-setup we can no longer afford having users work off of the nightlies for months between releases. From 1.0 onwards we’ll have bi-weekly releases, not necessarily coupled to any massive feature updates. This will allow you to work off of a frozen and up-to-date release. Currently, if you work off the nightlies, you have to store that nightly version on your end.
We’ll consider semantic versioning for our next releases. However, i do believe that it’s not a 100% fit for us. We’ll stay at major version 1 for the foreseeable future. We’ll increase the minor version on API changes, and the patch version for bug fix releases. This may mean we’d arrive at something like 1.2.10 at some point (meaning we created 10 bug fix releases without API changes :)).
With the 1.0 release we’ll also remove support for the gdx-setup-ui that generated Eclipse projects. Maintaining two things that do the same is always a bad idea. Our Gradle project generator is really nice now, the workflows in the different IDEs work pretty well, and the general experience is just better. We still have a few things to iron out, but we believe this can be done until next weekend.
I’m not sure i can do something special for 1.0, so please don’t expect anything