June 9th, 2013 at 4:50 PM
People forget that Minecraft is a rolling release type - it's continually developing. In actuality, the snapshot versions make it part-rolling (one stable version which is a rolling upgrade - but several unstable versions for testing which are updated regularly and implemented into the stable build when they're ready.) But if they were going to do that, they should have gone straight from alpha to release.
With my project I plan for the official release to be part-rolling. It will have one stable core version as well as various beta unstable updates (or if new features are going to be added, it'll use release-candidates.) This way, people who want to use the core stable version don't have to update so often, but people who want to see new features and bug fixes ahead of time may want to op to update frequently. This is of course optional, any and all versions will remain available long after release and even after support for them has ended - even the unstable testing versions. So one can continue using the same version for as long as they'd like and go back to any version that they want whenever they'd like.
Sorry for the drawn out post
With my project I plan for the official release to be part-rolling. It will have one stable core version as well as various beta unstable updates (or if new features are going to be added, it'll use release-candidates.) This way, people who want to use the core stable version don't have to update so often, but people who want to see new features and bug fixes ahead of time may want to op to update frequently. This is of course optional, any and all versions will remain available long after release and even after support for them has ended - even the unstable testing versions. So one can continue using the same version for as long as they'd like and go back to any version that they want whenever they'd like.
Sorry for the drawn out post
