I plan on branching the code for Heat of the Race off of Battle Machines. This will probably mean that Heat of the Race will allow for people to register before the game is playable. However, there won’t be any advertising, so the people who happen to just stumble across the site should be minimal. I’ll probably do most of the development work off of the Battle Machines repository on a branch. By the time I import the branch into the Heat of the Race repository, most of the work should be finished and so should the template.
When I stop development on Battle Machines, I should just have to work on the game elements and not have to worry about the user components and start pages. Most of the game elements will be finished also, since Battle Machines and Heat of the Race will share similar traits with a few only a few differences.
HEAT Development Cycle
I plan on developing Battle Machines for two to three months, completing as much as the start and user components as possible. I should also get as much game features done also.
As much time as I put into Battle Machines should also translate into less time I have to place into HEAT. The development I place into HEAT should also be transferable to Battle Machines, depending on the feature. Any fixes or new features added to the start and user components should safely be able to transfer over without breaking anything.
Repositories
The usage of repositories should reduce the amount of conflicts from other developers changes. The other developers aren’t currently using the repositories, but that should change when all of the new development is switched over. As easy as it is to use Subversion, I see no reason why they can’t get accustomed to using the repositories.
Possibly Related Posts:
- Dragon MVC
- Why I Contributed to WordPress
- DragonU DB Component
- Working On My WordPress Plugins
- Hurray! I’m Back!
Tags: Battle Machines, Heat Of The Race