frc3175/deep-space

This is a premade repository to test the slack GitHub bot and to post the FRC 2019 game robots code

deep-space's Issues

Version Numbers

Versions

Versions are organized and listed by Release version (Alpha, Beta, and Full release), primary version, secondary version, and finally the tertiary version. Examples Versions are listed below
{Alpha 0.1.12}
{Beta 0.3.42}
{Full Release 1.3.23}

Release Version

Deciding the release version is actually quite simple. But first, one must conclude; how well the version has been tested, the time between releases, and whether the code has been peer-reviewed.

If the code has just been tested by the programmer, the version is Alpha. If the code has been tested by the programmer, and the operator/driver, the version is Beta. If the code has been tested by the programmer, the operator/driver, and a build team member (Often the build team member happens to be a driver/operator), the version will be Full Release.

The time between release requirement is there to prevent premature, unchecked, swift releases from being confused as a full release. Give at least 30 minutes between release time to fine-tune your code. (Hotfixes are an exception).

Primary, Secondary, and Tertiary version numbers

The primary version is rarely changed unless a drastic change has been done. This would include but not limited to a total bot redesign where code needs to be changed, and a large mechanic change. For example, if suddenly a scissor lift is not working and needs to be removed and code changed, it will warrant a primary version change.

The secondary version is changed for anything that is added or removed. This would include changes such as adding an electric gear or changing the number of motors.

The tertiary version is changed anytime a bug, port number, or other small changes have been made. This would include fixing a faulty line of code and changing the victor's output.

Rule of Thumb for Version Numbers

• The primary version starts at 0 but the secondary and tertiary start at 1.
• You should try to hit full release before a competition
• It's easy to advance to beta... so do it.
• Include every change you make in the commit on GitHub