This wiki is archived and useful information is being migrated to the main bzflag.org website
Difference between revisions of "Development RoadMap"
(→3.0 (Next Major)) |
(tree up the versions to show compatiblity) |
||
| Line 5: | Line 5: | ||
Individual features may move up or down the roadmap depending on how/when they get done. Entire releases may be pushed up the roadmap or merged depending on how development goes. | Individual features may move up or down the roadmap depending on how/when they get done. Entire releases may be pushed up the roadmap or merged depending on how development goes. | ||
| − | ==2.4.0 (Wake the dead)== | + | ==2.4== |
| + | ===2.4.0 (Wake the dead)=== | ||
2.4 will be the next release of BZFlag and is protocol incompatible with all previous versions. | 2.4 will be the next release of BZFlag and is protocol incompatible with all previous versions. | ||
The development goals are listed here [[BZFlag 2.3]] | The development goals are listed here [[BZFlag 2.3]] | ||
| − | ==2.4.2 (What was once lost)== | + | ===2.4.2 (What was once lost)=== |
2.4.2 will be the first maintenance release of the 2.4.x compatibility line. Its primary function is to fix bugs found in the 2.4.0 release and to include non breaking items that were not ready during the initial release including: | 2.4.2 will be the first maintenance release of the 2.4.x compatibility line. Its primary function is to fix bugs found in the 2.4.0 release and to include non breaking items that were not ready during the initial release including: | ||
| Line 15: | Line 16: | ||
* Fastmap | * Fastmap | ||
| − | ==2.4.4 (Making the stride)== | + | ===2.4.4 (Making the stride)=== |
* New Death effects | * New Death effects | ||
* HTTP Management plugins | * HTTP Management plugins | ||
| Line 24: | Line 25: | ||
* New Translations | * New Translations | ||
| − | ==2.4.x (Maintenance)== | + | ===2.4.x (Maintenance)=== |
Continuing releases to fix critical bugs. New features should go into 2.6 at this point. | Continuing releases to fix critical bugs. New features should go into 2.6 at this point. | ||
| Line 41: | Line 42: | ||
* Things added in V3 that were not back-ported. | * Things added in V3 that were not back-ported. | ||
| − | ==3.2 ( | + | ===3.0.2 ( End user cleanup )=== |
| + | Compatible release ( if possible ) that makes the game easier for new users to play and for servers to manage players. | ||
* UI Cleanup | * UI Cleanup | ||
| − | |||
* New Group and user Management. | * New Group and user Management. | ||
| + | * In game registration | ||
| + | * Tutorials | ||
| + | |||
| + | ==3.2 (Modernization)== | ||
| + | * Lag compensation | ||
* Threaded Networking | * Threaded Networking | ||
* Threaded Simulation | * Threaded Simulation | ||
Revision as of 19:52, 7 June 2011
Contents
Overview
This document discusses the general development road-map for Future BZFlag Releases.
Features
Individual features may move up or down the roadmap depending on how/when they get done. Entire releases may be pushed up the roadmap or merged depending on how development goes.
2.4
2.4.0 (Wake the dead)
2.4 will be the next release of BZFlag and is protocol incompatible with all previous versions. The development goals are listed here BZFlag 2.3
2.4.2 (What was once lost)
2.4.2 will be the first maintenance release of the 2.4.x compatibility line. Its primary function is to fix bugs found in the 2.4.0 release and to include non breaking items that were not ready during the initial release including:
- BZFScron
- Fastmap
2.4.4 (Making the stride)
- New Death effects
- HTTP Management plugins
- Push Stats
- Bug fixes
- New Font System
- New Server List
- New Translations
2.4.x (Maintenance)
Continuing releases to fix critical bugs. New features should go into 2.6 at this point.
2.6 (Next Breaking Release)
This version may be rolled into the 3.0 release if that code base is still usable. If the code is extended from 2.4 it may have these features;
- Lua
- Acceleration changes
- Flag Drop "Zone" feature
3.0 (Next Major)
Using the 2.99 continuing branch, or the 2.6 branch with a lot of backports depending on codebase stability.
- Consistent collisions on all world objects (treat them as meshes?).
- New Simulation
- Shot Type/Flag Type split
- Things added in V3 that were not back-ported.
3.0.2 ( End user cleanup )
Compatible release ( if possible ) that makes the game easier for new users to play and for servers to manage players.
- UI Cleanup
- New Group and user Management.
- In game registration
- Tutorials
3.2 (Modernization)
- Lag compensation
- Threaded Networking
- Threaded Simulation
3.4 (Server State)
- Server Side Shots
- Server Side Deaths
