ScalarNext/About - Revision history

Xor: update

2018-02-21T14:06:57Z

update

Xor: /* Simple Versioning */ fix

2018-02-05T13:39:27Z

Simple Versioning: fix

Xor: Initial commit

2018-02-05T13:37:39Z

Initial commit

New page

{{Navbox small
| title = ScalarNext Sub-pages
| parent = ScalarNext
| page1 = Version History
| page2 = 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 with the biggest found being 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.

@@ Line 7: / Line 7: @@
 ----
-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.
+;What's special about it?
+:Nothing. Really? Let's see...

@@ 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.
-During the days of [[SimpleBot]] and [[ScalarBot]], I experimented several different versioning schemes, and with the biggest found being 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.
+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.