Create build script, warnings in bl_info, tools using arg_parser

[tngreene]

Currently we have a new_version script (that in my opinion needs to not automatically do all the git work for you), to replace addon version numbers. A new script is needed to generate and replace the build number, and write in the "warning" entry in the bl_info dictionary, in case people read that. They probably won't, but, its part of the spec I wanted.

The build script should write a log of builds as a .csv featuring the number, notes, etc.

Without this, only a moderate improvement over simply having an addon number will exist, and doing things by hand will still by prevalent.

Even better would be some githooks that automatically change build_types based on if the branch is coming off of a beta branch or not.

• New build script that automatically creates zip files!
• Can replace Major, Minor, Revision, Build Type, Build Number, Data Model Number, Build Number!
• Runs the test suite with arbitrary arguments
• Can replace bl_info['warning']
• Can make git tags (not a high priority)
• Extremely well tested
• Writes .csv build log We're not doing that anymore

[tngreene]

In addition, using arg_parser from now on and actually using the if name == "main" pattern would be a nice touch.

[tngreene]

Also, build tools and tests.py must be Python 2.7 compatible unless there is a really really great reason for them not to be because some people's envs aren't set up with Python 3. Nope! Modern modern modern now!

[tngreene]

New game: Increment this comment everytime you get burned by having to manually do this. Just now I recently realized that 3.5.0-beta.1 has DEV in its config.

Number of releases and builds that suffered "Squishy Human Brain" issues:

12!

(12 seems like a reasonable guess to start with)

[tngreene]

Now that we have a build script that works, setting priority low, because this is something that is just going to get better over time.

[tngreene]

Closing this and making 2 new bugs. We made it, we're using it right now, "extremely well tested" is a principle applied to every piece of software and I can't devote anymore time to this. Well tested will just come from using it.

YAY, we made it!!!