Thursday, April 18, 2013

JCDC 4 digit Version System (Versioning)

The 4 Digit Build Number Versioning System

Here is how I think  we should do the 4 digit build numbering system



A.B.C.D



A = Major version number, I.e. Each time you do a complete rewrite, increment this number.



B = Breaking Change Number. Each time you release a change that will require your users to change their code, increment this number.
       (For Nuget Packages, we increment this package only for the one that's altered manually, If package A causes a change in package B, but B does not cause a change to package C, only A has a breaking change)



C = Production Build Number = Each time you release to prod, increment this number.
       (For Nuget Packages, we ignore this number)



D = Dev\QA Build Number Each time you build to go to QA increment this number.
       (For Nuget Packages, we only increment this number)




Offical JCDC Description:


Note: Follow these rules to increment the version numbers:

X.x.x.x - We increment the leftmost digit by one when we make major changes to the apps (such as from 2G to 3G)

x.X.x.x - We increment the second-to-the-left digit when we make significant changes to a JCDCHelper project that require code changes to the remaining JCDCHelper projects that depend on this one.

x.x.X.x - We increment the third-to-the-left digit when we make changes to a single JCDCHelper project that don’t require code changes to the other packages (but you still need to update the JCDCHelper projects that depend on this single project)


x.x.x.X - We increment the rightmost digit when we don’t make code changes to a single JCDCHelper project, only need to release that project.



Monday, April 15, 2013

NUGet error
 
I just used your solution copier tool (do eeet!) to get a working start on a jcdchelper project.  Now I’m trying to redo the nuget packages, but package manager console is giving me


Arithmetic operation resulted in an overflow.


Current Theory - You typed the Path with the wrong case when you had the tool rename the project, OR the tool itself renamed the project. so JCDC Heleper Becase JcdcHelper or something similar causeing the paths to be internally inconsistant in the project.


First attempt: edit the nuget.config file to fix teh capitalization error.

Second Attempt:
1 Delete all teh packages.config files, copy from a working project and modify by hand.

retest.


3rd attempt

if no joy, Manually remove all nuget stuff from all projects (ncludeing refereces) and rebuild it by hand. this worked for Jeffery