Difference between revisions of "ScalarNext/About"
(Initial commit) |
m (→Simple Versioning: fix) |
||
| Line 10: | Line 10: | ||
While mainstream software is traditionally versioned in x.y.z where x is major, y is minor, and z is patch, bots in robocode are often versioned in a wide variety of ways. That's not because robot authors aren't familiar with the traditional ways, since even some experienced software engineers are using custom versioning for robots. | While mainstream software is traditionally versioned in x.y.z where x is major, y is minor, and z is patch, bots in robocode are often versioned in a wide variety of ways. That's not because robot authors aren't familiar with the traditional ways, since even some experienced software engineers are using custom versioning for robots. | ||
| − | During the days of [[SimpleBot]] and [[ScalarBot]], I experimented several different versioning schemes, and | + | During the days of [[SimpleBot]] and [[ScalarBot]], I experimented several different versioning schemes, and end up realizing that robot development is really different from ordinary software development. In robocode, we not only develop the robots along the line, but also branch very often to test a wide variety of possibilities. A versioning system not covering this use case will be indeed not suitable for robot versioning. |
For the reasons above, a new versioning scheme called "Simple Versioning" (SimVer) is proposed here to suggest a way of versioning robots, especially those with a wide variety of branches. | For the reasons above, a new versioning scheme called "Simple Versioning" (SimVer) is proposed here to suggest a way of versioning robots, especially those with a wide variety of branches. | ||
Revision as of 14:39, 5 February 2018
- ScalarNext Sub-pages:
- ScalarNext - Version History - About
Simple Versioning
While mainstream software is traditionally versioned in x.y.z where x is major, y is minor, and z is patch, bots in robocode are often versioned in a wide variety of ways. That's not because robot authors aren't familiar with the traditional ways, since even some experienced software engineers are using custom versioning for robots.
During the days of SimpleBot and ScalarBot, I experimented several different versioning schemes, and end up realizing that robot development is really different from ordinary software development. In robocode, we not only develop the robots along the line, but also branch very often to test a wide variety of possibilities. A versioning system not covering this use case will be indeed not suitable for robot versioning.
For the reasons above, a new versioning scheme called "Simple Versioning" (SimVer) is proposed here to suggest a way of versioning robots, especially those with a wide variety of branches.
