This is my idea is for the road map to 1.0.0:
---------------------------------------------------------
0.5.0(current) -> 0.6.0
* clean the code
* document the api and code
* xmash/bfxm inpot/expot script for blender 2.5/2.6
* create new build system
* bug fix
* And a halt on the development on new features acept ipv6 stack and masterserver suport [link].
0.6.0 -> 0.7.0
* server announcements board
* start the development for a new economic engine
0.7.0 -> 0.8.0
* finish the development the new economic engine
* start the design new intervace and gui.
0.8.0 -> 0.9.0
* move to the sirikata engine
* Multiplayer admin backend
0.9.0 -> 0.9.5 (1.0.0 alpha)
* add new content (missions,ships,etc)
* start creating the first cutscene
* script the first few chapters of the main story line max 2
houres of game play.
* finish the first part of the story
0.9.5 -> 0.9.8 (1.0.0 beta)
* add the rest of the story
* create the game intro scene
* game balances
0.9.8 -> 1.0.0 (1.0.0 Release candidate)
* bug fix only
1.0.0 gold release
-------------------------------------------------
As you see in my road map proposol the target to 0.6.0 is clean and doument the code and sabelise the game.
But the reason is that we need to this is that for the meartch with the sirikata code base.
[idea]Road map to 1.0.0
-
- Venturer
- Posts: 537
- Joined: Sat May 14, 2005 10:51 am
- Location: milkyway->the sol system->earth->Europe->The Nederland->Soud Holland->Leiden
- Contact:
[idea]Road map to 1.0.0
All Your Base Are Belong To Us
-
- Elite
- Posts: 8014
- Joined: Fri Sep 05, 2003 4:03 am
- Location: Montreal
- Contact:
Re: [idea]Road map to 1.0.0
I'd suggest "create new build system" be the top priority.www2 wrote:0.5.0(current) -> 0.6.0
* clean the code
* document the api and code
* xmash/bfxm inpot/expot script for blender 2.5/2.6
* create new build system
* bug fix
* And a halt on the development on new features acept ipv6 stack and masterserver suport http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/trunk/masterserver/api.txt?revision=12545&view=markup[link.
Clean the code should be a high priority, but it's a huge amount of work; I think something along the lines of a clean-up is more likely to happen with a more targeted goal, like 'clean up flight system', or 'clean up the mission system'.
I'd also like to suggest cube-map support be moved to the URGENT category; it's almost done, AFAIK, and it would have a greater impact on game visuals than anything else I can think of.
My suggested revised 0.6:
0.5.0(current) -> 0.6.0
* create new build system
* cube-map support
* clean <some specific-> code
* document the api and code
* xmash/bfxm inpot/expot script for blender 2.5/2.6
* bug fix
* And a halt on the development on new features acept ipv6 stack and masterserver suport
http://vegastrike.svn.sourceforge.net/v ... iew=markup
Latest version of Cinemut Opaque
Latest version of LaGrande noodleworks (scroll down).
An evolving La Grande How-To...
The non-working, but latest, CineMut test_bike
PU (Privateer: Parallel Universe's Home). WC or Privateer Drayman for you?
WCpedia --The Wing Commander Encyclopedia-- From Angel Deveraux through Belisarius to Zachary Banfeld...
WC Nexus forum, the Moonbase Tycho of WC fans.
Latest version of LaGrande noodleworks (scroll down).
An evolving La Grande How-To...
The non-working, but latest, CineMut test_bike
PU (Privateer: Parallel Universe's Home). WC or Privateer Drayman for you?
WCpedia --The Wing Commander Encyclopedia-- From Angel Deveraux through Belisarius to Zachary Banfeld...
WC Nexus forum, the Moonbase Tycho of WC fans.
-
- Elite Mercenary
- Posts: 1329
- Joined: Thu Mar 27, 2003 11:51 pm
- Location: Manchester, UK
- Contact:
Re: [idea]Road map to 1.0.0
I disagree with the roadmap beyond the 0.5.x series. It's falling into the main roadmap trap of trying to predict the future and narrow focus on things when contributions are dynamic and driven by interest.
0.5.1, 0.5.2, 0.5.x should all be save game compatible. Breaking save games then branch for 0.6.x and do pre-releases until the format is stabilized.
The major thing missing from www2's 0.5.x roadmap is integrating unused quality models. Fendorin has done a load.
0.5.0(current) -> 0.5.x
* integrate models/media
* clean the code
* document the API and code
* xmash/bfxm import/export script for blender 2.5/2.6
* create new build system [fix safemode's cmake system?]
* bug fix
* And a halt on the development on new features except ipv6 stack and masterserver support [why these two features?]
0.5.1, 0.5.2, 0.5.x should all be save game compatible. Breaking save games then branch for 0.6.x and do pre-releases until the format is stabilized.
The major thing missing from www2's 0.5.x roadmap is integrating unused quality models. Fendorin has done a load.
0.5.0(current) -> 0.5.x
* integrate models/media
* clean the code
* document the API and code
* xmash/bfxm import/export script for blender 2.5/2.6
* create new build system [fix safemode's cmake system?]
* bug fix
* And a halt on the development on new features except ipv6 stack and masterserver support [why these two features?]
Free Gamer - free software games compendium and commentary!
FreeGameDev forum - open source game development community
FreeGameDev forum - open source game development community
-
- Elite
- Posts: 1363
- Joined: Sat Aug 04, 2007 3:42 pm
Re: [idea]Road map to 1.0.0
Yeah I agree; for example there are many things people could want to do to enhance combat and exploration/navigation in future releases, not just trade. And then you have dynamic factions and missions and a million other possibilities.charlieg wrote:I disagree with the roadmap beyond the 0.5.x series. It's falling into the main roadmap trap of trying to predict the future and narrow focus on things when contributions are dynamic and driven by interest.