[Openlancer-programming] Reorganization

[erik m. <eri...@gm...>]

Its time for a programming reorganization. The release-oriented to-do-lists
have been scrapped in favor of a much more flexible general to-do-list that
is instead focused on releasing whenever the programmers feel like it, and
doing frequent maintenence releases. The new version system reflects this:

0      .      0      .      3      .      0

^- Openlancer major version, tied in with minor version. Examples:
Openlancer 0.1 will be the fully playable
Arena release, 0.4 or 0.5 will be Freelancer functionality, and we all know
what 1.0 and 2.0 mean.

               ^- Openlancer minor version. See above.

                              ^- Openlancer release number. Corresponds to
the current source release. Reset
                                  to 0 when minor version is increased.

                                              ^- Maintence version.
Corresponds to Maitenence releases.
Programmers will work on whatever i tell them to work on, or just anything
if they don't have specific instructions, and items will be frequently added
and removed. Instead of having items being checked off, items will be simply
removed from the list. In general the list only reflects improvements we
want to put in very soon, and almost never goes past the next release (but
as you can see, the list branches across several maintenence releases)
Naming format for file releases:

OpenL_0.0.3M0.zip

Basically, OpenL_, plus the major, minor and release version numbers, an M,
and then the maintenence version.
-- 
Sincerely, Blackhole - Lead Programmer