Difference between revisions of "DevelopmentPlans/2.3"

From BZFlagWiki
Jump to: navigation, search
(Backports)
(Added section for trivial/polish features)
Line 84: Line 84:
 
* New Translations
 
* New Translations
 
* Map geometry changes ( requires flag zap zone support or breaks existing servers. )
 
* Map geometry changes ( requires flag zap zone support or breaks existing servers. )
 +
 +
==Trivial/Polish features==
 +
The following limited number of trivial/non-invasive new features or changes should be considered for implementation before the final stable release. These may already exist as patches which were rejected because they were for branch rather than trunk.
 +
 +
* Countdown/reload timer position fix for when showCoordinates is enabled

Revision as of 21:21, 11 May 2011

BZFlag 2.3 will be a development version intended to sidestep the abandonment of BZFlag 3.0 development.

Goal

The goal is to release a new version of BZFlag that is incompatible with 2.0.x for a good reason, and has at least one new feature that will make many players want to upgrade.

The hope is that this process will renew developer motivation and attract new developers.

Note: This proposal requires changing the version docs to make the compatability be the minor version number.

General ideas

  • Facilitate moving global services (e.g., my.bzflag.org) to new hardware.
  • Add one or two non-trivial client features so the players will be motivated to upgrade
 - graphics quality?
 - server list backport?
 - Cloaked Shot flag (hoping for better than this)
  • anti-cheating?
  • Fix the protocol bug that version 2.0.16 was a bandaid for.
  • Remove the /identify command.
  • BZBB rank promotions! ;-)

Schedule

  • Immediately open 2.0.17 up for whitespace, Subversion properties, copyright notices, and other easy changes that don't break protocol.
  • Solicit specific change proposals that can be completed within one month. Each proposal must be sponsored by an individual developer who will lead its implementation.
  • When proposals are in and accepted by consensus, start the 1-month countdown clock.
  • Copy trunk to a V3_FAIL tag.
  • Copy v2_0branch to trunk and commit a change that requires a new protocol number.
  • Implement accepted proposals and test.
  • After 1 month, revert any changes that have caused unfixed regressions.
  • Update version docs and make trunk into 2.4.0.0 for releease.
  • Tag Trunk to 2_4branch trelease.

Backports

These items should be moved back from V3 into the new version.

  • Connection Header Change
  • Round Robin for services
  • New GUI elements
  • Server Side Scoring
  • Sim loop breakup (to prevent F5)
  • Server Side Flag ID and pickup
  • New Shot Graphics
  • Hud Markers
  • Removal of low graphics, promotion of experimental to high.
  • Server List from SOC
  • API rework
  • Remove Identify
  • Windows Project Cleanup
  • New Make system
  • New source docs ( authors etc..)
  • Server side handicap
  • Gm shot checks
  • Stealth fixes for rabbit
  • Screenshot fixes
  • Update Notification
  • Wings Velocity Change
  • Message Protection
  • New artwork
  • no Tks
  • open FFA
  • download URL change ( to force just images.bzflag.org, not any .org or .bz )
  • remove fog options ( let server force)
  • require GL 1.2

Backport evals

These items should be evaluated to see if they can be or should be moved back, but are not critial.

  • Map changes.
  • HTTP plugins
  • New API events
  • BZFChron
  • Server Side Players
  • Bugfixs not in notes
  • New flags
  • Rabbit as team

Things NOT to backport

These items should not be moved back due to stability issues. These are generaly be the blocking items preventing V3s current release.

  • Network buffering
  • Lua
  • Lag Comp
  • Acceleration Changes
  • Font System
  • New Translations
  • Map geometry changes ( requires flag zap zone support or breaks existing servers. )

Trivial/Polish features

The following limited number of trivial/non-invasive new features or changes should be considered for implementation before the final stable release. These may already exist as patches which were rejected because they were for branch rather than trunk.

  • Countdown/reload timer position fix for when showCoordinates is enabled