Re: NCX: ArrayMax, ArrayMin: unexpected values
Posted: 03 Jul 2011, 15:01
why not take
1.31
1.3101
1.3102
1.3103
1.3104
1.31
1.3101
1.3102
1.3103
1.3104
Give a child a robot, he'll play for an hour. Teach him to build, and he'll play forever.
https://mindboards.org:443/
From my experience with our mindstorms software and hundreds of students, as well as other software projects: Never have two different releases or versions of your software with the same version number / identifier. Things can get really ugly. If you don't want to change the major version number or the identifier string, that's ok. But you GOT to have some sort of unique identifier in software products, period! You can use a build-number, the SVN-Revision, or a date. But it must be something unique for each version (as in FW image / zip file) that you create. That's just good craftmanship. My centsafanofosc wrote:I will probably someday increment the firmware version number. Please forgive me for not wanting to completely deviate from the version number of the standard firmware from which the enhanced firmware was created.