Minecraft versions

[ShooShoSha]

Make branches corresponding to the promoted version of minecraft. For example, separate branches for 1.6.4 and 1.7.2 for development.

Whichever version is the group develops, (i.e. most of us develop in 1.7.2 as of this posting) make the corresponding branch the default branch. See CoreModding/Craftable-Enchantments#8 for a reference.

This problem is associated with several issues:
CoreModding/CORE-API#2
#1

[ShooShoSha]

Current master branches need to be merge with a new branch with an appropriate version name.

[ShooShoSha]

@zeuslightning125 Why were these tickets closed without actually being addressed? The branch names need to be labeled to reflect the version.

Eh... I really think it's fine as long as master is the main dev version and the side branches are releases of previous versions or concurrent builds. At least that's what I was thinking when I came up with the multiple branches thing.

I guess we could rename master, but I dont see how it matters. If you really think it's important, I can go around and do that for all of those.

[ShooShoSha]

The latest stable build of code will be merged with either a release or a master branch. Upon a successful merge, tag the branch with an appropriate versioning scheme: minecraft_version-mod_version is needed.