What was the rationale to jump straight to 1.7.4? All I can see from the 1.7.4 pre-release is that it solved 3 bugs over the 65 bugs solved in 1.7.3 pre-release plus the two new features; Twitch support and Chicken Jockeys.
I'm dumbfounded.
Rollback Post to RevisionRollBack
I was trying to think of a signature and this is what came up.
What do you think it's going to get to this time? It might reach 1.7.7. Maybe they have to change the version number if they were planning to release it but then ran into several more problems, even if they didn't take long to fix.
My guess is to avoid confusion with beta 1.7.3, but who knows. They jumped straight from 1.7 pre-release versions to 1.7.2 as a release, they skipped 1.6.3 as well. Minecraft version numbers don't seem to follow the typical software development path, so your guess is as good as mine.
What was the rationale to jump straight to 1.7.4? All I can see from the 1.7.4 pre-release is that it solved 3 bugs over the 65 bugs solved in 1.7.3 pre-release plus the two new features; Twitch support and Chicken Jockeys.
Guess this time they are just doing the even numbers
There was a
1.7 pre-release. They found a bug before release, so they made a
1.7.1 pre-release. They found a bug before release, so they made a
1.7.2 pre-release. No game-breaking bugs were found this time, so then
1.7.2 full release became available soon after.
Later on, they made a
1.7.3 pre-release. They found a bug before release, so they made a
1.7.4 pre-release. No game-breaking bugs were found, and so
1.7.4 full release was made available.
There was a
1.7 pre-release. They found a bug before release, so they made a
1.7.1 pre-release. They found a bug before release, so they made a
1.7.2 pre-release. No game-breaking bugs were found this time, so then
1.7.2 full release became available soon after.
Later on, they made a
1.7.3 pre-release. They found a bug before release, so they made a
1.7.4 pre-release. No game-breaking bugs were found, and so
1.7.4 full release was made available.
Make sense?
Sure, but why even have 'pre-release' when they have development snapshots? Aren't all the snapshots basically a form of pre-release?
There was a
1.7 pre-release. They found a bug before release, so they made a
1.7.1 pre-release. They found a bug before release, so they made a
1.7.2 pre-release. No game-breaking bugs were found this time, so then
1.7.2 full release became available soon after.
Later on, they made a
1.7.3 pre-release. They found a bug before release, so they made a
1.7.4 pre-release. No game-breaking bugs were found, and so
1.7.4 full release was made available.
Make sense?
1.7.2 was a release...
1.7.4 will be a release.
Even number release.
Made sense before I made the joke, makes sense after.
Sure, but why even have 'pre-release' when they have development snapshots? Aren't all the snapshots basically a form of pre-release?
Pre-releases are intended to allow modders to get their code ready for the update ahead of time. If a pre-release is final, then the modder can update their mods while waiting for the official release.
Sure, but why even have 'pre-release' when they have development snapshots? Aren't all the snapshots basically a form of pre-release?
Basically? Basically, yeah. But not totally the same. Snapshots aren't intended to be complete and ready. Pre-releases are, ideally. Snapshot means "hey we know it's not finished yet, but here are some of the new features we've been working on." Pre-release means "we think we're done, so if nothing comes up in the meantime, this'll be the version we release next week."
They update version numbers during snapshots to distinguish better when protocol changes happen.
1.7.3 originally had a protocol change, so 1.7.4 helps ensure users know they can connect to 1.7.2, since it was reverted.
There was a case where SOME 1.7.3 can connect but other versions of 1.7.3 could not, so yes, very rationale.
What? No, I...wait, what? Are you implying that 1.7.4 clients can connect to 1.7.2 servers...because they both have even numbers at the end!?!?! I don't think that's it, at all...
Basically? Basically, yeah. But not totally the same. Snapshots aren't intended to be complete and ready. Pre-releases are, ideally. Snapshot means "hey we know it's not finished yet, but here are some of the new features we've been working on." Pre-release means "we think we're done, so if nothing comes up in the meantime, this'll be the version we release next week."
Sure, that makes sense. My point is rather that it's not really necessary to increment the release versions during pre-releases. Why not just name it 13w50pr1, 13w50pr2 etc. and when they get a stable one, then release 1.7.x? I have no background in software development and version numbers, so I'm not trying to argue here, I'm just curious. To me, incrementing the version number is saying, 'hey, here's a version that is different from the last released version' not 'hey, here's a version that's different from the last not-released version'. That's just how I've always thought it worked, but I'm probably wrong.
Sure, that makes sense. My point is rather that it's not really necessary to increment the release versions during pre-releases. Why not just name it 13w50pr1, 13w50pr2 etc. and when they get a stable one, then release 1.7.x? I have no background in software development and version numbers, so I'm not trying to argue here, I'm just curious. To me, incrementing the version number is saying, 'hey, here's a version that is different from the last released version' not 'hey, here's a version that's different from the last not-released version'. That's just how I've always thought it worked, but I'm probably wrong.
I see what you mean, and I agree. But note that they would have to change the naming mechanism. 13wXX wouldn't work, because under their nomenclature, XX stands for the week number.
Personally, I find their Snapshot naming mechanism too convoluted for my taste. Weekly snapshots are akin to daily builds in most open source software (and some closed source). The naming mechanism used in that software usually follows the normal versioning system with an extra dot denoting the daily build number. 1.7.2.5 would stand for version 1.7.2, snapshot number 5. But hey, it's their prerogative if they want to do it another way. It's just that naming the week number is as useless information as it can get. Versioning software already informs the developers on the date of a release and users don't care for anything other than incremented numbers. So... yeah.
So, following your reasoning, we could have, for instance, a number of 1.7.2.X snapshots, followed by a 1.7.3.p1 pre-release, followed by a 1.7.3 final release. If the pre-release failed, they would go back to 1.7.2.X+1, and later 1.7.2.p2, et cetera, until they got the 1.7.3 final release. This I would find a simpler naming mechanism. But this is all rather moot. To each its own and I'm sure not everyone would want to do it this way. It's also besides the point.
Seems to me they just skipped because they can. Or there is some internal (weird) policy that when a pre-release fails they increment the release number.
Rollback Post to RevisionRollBack
I was trying to think of a signature and this is what came up.
Personally I would simply release more RCs for a particular upcoming version if necessary, but whatever floats Mojang's boat I guess, if it makes sense to them to skip a version if its first (and apparently only) RC fails then that is their thing.
Sure, but why even have 'pre-release' when they have development snapshots? Aren't all the snapshots basically a form of pre-release?
the snapshots are so they can have player feedback at every step of the way, so they aren't really a prerelease, as they only add a small portion of stuff to the game that may be added or may be taken out.
Pre-releases are just them telling you that they think the current snapshot is going to be the full release. (No changes unless some show-stopping bugs are found.) They are snapshots, but they are snapshots that they think are ready for full release.
I'm dumbfounded.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Retired Staffhttps://twitter.com/Dinnerbone/status/410022933323849728
Minecraft-things: http://skylinerw.com
More Minecraft-things: https://sourceblock.net
Guides for command-related features (eventually moving to Source Block): https://github.com/skylinerw/guides
I primarily hang out in the /r/MinecraftCommands discord, where there's a lot of people that help with commands: https://discord.gg/QAFXFtZ
Their corresponding subreddit: https://www.reddit.com/r/MinecraftCommands/
Guess this time they are just doing the even numbers
There was a
1.7 pre-release. They found a bug before release, so they made a
1.7.1 pre-release. They found a bug before release, so they made a
1.7.2 pre-release. No game-breaking bugs were found this time, so then
1.7.2 full release became available soon after.
Later on, they made a
1.7.3 pre-release. They found a bug before release, so they made a
1.7.4 pre-release. No game-breaking bugs were found, and so
1.7.4 full release was made available.
Make sense?
Village Mechanics: A not-so-brief guide - Update 2017! Now with 1.8 breeding mechanics! Long-overdue trading info, coming soon!
You think magic isn't real? Consider this: for every person, there is a sentence -- a series of words -- which has the power to destroy them.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumSure, but why even have 'pre-release' when they have development snapshots? Aren't all the snapshots basically a form of pre-release?
1.7.2 was a release...
1.7.4 will be a release.
Even number release.
Made sense before I made the joke, makes sense after.
-
View User Profile
-
View Posts
-
Send Message
Retired StaffPre-releases are intended to allow modders to get their code ready for the update ahead of time. If a pre-release is final, then the modder can update their mods while waiting for the official release.
Minecraft-things: http://skylinerw.com
More Minecraft-things: https://sourceblock.net
Guides for command-related features (eventually moving to Source Block): https://github.com/skylinerw/guides
I primarily hang out in the /r/MinecraftCommands discord, where there's a lot of people that help with commands: https://discord.gg/QAFXFtZ
Their corresponding subreddit: https://www.reddit.com/r/MinecraftCommands/
1.7.3 originally had a protocol change, so 1.7.4 helps ensure users know they can connect to 1.7.2, since it was reverted.
There was a case where SOME 1.7.3 can connect but other versions of 1.7.3 could not, so yes, very rationale.
Creator of Timings - Open Source Enthusiast - Mentor - Discord: Code With Aikar, PaperMC
Server Owners: Proven Optimized Server Startup Flags
Basically? Basically, yeah. But not totally the same. Snapshots aren't intended to be complete and ready. Pre-releases are, ideally. Snapshot means "hey we know it's not finished yet, but here are some of the new features we've been working on." Pre-release means "we think we're done, so if nothing comes up in the meantime, this'll be the version we release next week."
What? No, I...wait, what? Are you implying that 1.7.4 clients can connect to 1.7.2 servers...because they both have even numbers at the end!?!?! I don't think that's it, at all...
Village Mechanics: A not-so-brief guide - Update 2017! Now with 1.8 breeding mechanics! Long-overdue trading info, coming soon!
You think magic isn't real? Consider this: for every person, there is a sentence -- a series of words -- which has the power to destroy them.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumSure, that makes sense. My point is rather that it's not really necessary to increment the release versions during pre-releases. Why not just name it 13w50pr1, 13w50pr2 etc. and when they get a stable one, then release 1.7.x? I have no background in software development and version numbers, so I'm not trying to argue here, I'm just curious. To me, incrementing the version number is saying, 'hey, here's a version that is different from the last released version' not 'hey, here's a version that's different from the last not-released version'. That's just how I've always thought it worked, but I'm probably wrong.
I see what you mean, and I agree. But note that they would have to change the naming mechanism. 13wXX wouldn't work, because under their nomenclature, XX stands for the week number.
Personally, I find their Snapshot naming mechanism too convoluted for my taste. Weekly snapshots are akin to daily builds in most open source software (and some closed source). The naming mechanism used in that software usually follows the normal versioning system with an extra dot denoting the daily build number. 1.7.2.5 would stand for version 1.7.2, snapshot number 5. But hey, it's their prerogative if they want to do it another way. It's just that naming the week number is as useless information as it can get. Versioning software already informs the developers on the date of a release and users don't care for anything other than incremented numbers. So... yeah.
So, following your reasoning, we could have, for instance, a number of 1.7.2.X snapshots, followed by a 1.7.3.p1 pre-release, followed by a 1.7.3 final release. If the pre-release failed, they would go back to 1.7.2.X+1, and later 1.7.2.p2, et cetera, until they got the 1.7.3 final release. This I would find a simpler naming mechanism. But this is all rather moot. To each its own and I'm sure not everyone would want to do it this way. It's also besides the point.
Seems to me they just skipped because they can. Or there is some internal (weird) policy that when a pre-release fails they increment the release number.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThanks for the explanation
the snapshots are so they can have player feedback at every step of the way, so they aren't really a prerelease, as they only add a small portion of stuff to the game that may be added or may be taken out.
I'm up to date on Homestuck if that matters :I