New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create build script, warnings in bl_info, tools using arg_parser #307

Closed
tngreene opened this Issue Sep 26, 2017 · 5 comments

Comments

Projects
None yet
1 participant
@tngreene
Copy link
Collaborator

tngreene commented Sep 26, 2017

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 tngreene added this to the v3.4.1 milestone Sep 26, 2017

@tngreene tngreene self-assigned this Sep 26, 2017

@tngreene

This comment has been minimized.

Copy link
Collaborator

tngreene commented Apr 23, 2018

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

@tngreene tngreene changed the title Create build script, warnings in bl_info Create build script, warnings in bl_info, tools using arg_parser Apr 23, 2018

@tngreene

This comment has been minimized.

Copy link
Collaborator

tngreene commented Apr 23, 2018

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

This comment has been minimized.

Copy link
Collaborator

tngreene commented Jul 24, 2018

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 tngreene added priority low and removed priority high labels Aug 9, 2018

@tngreene

This comment has been minimized.

Copy link
Collaborator

tngreene commented Aug 9, 2018

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

This comment has been minimized.

Copy link
Collaborator

tngreene commented Aug 15, 2018

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!!!

@tngreene tngreene closed this Aug 15, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment