This wiki is archived and useful information is being migrated to the main bzflag.org website

Editing DevelopmentPlans/2.3

Jump to: navigation, search

Warning: The database has been locked for maintenance, so you will not be able to save your edits right now. You may wish to copy and paste your text into a text file and save it for later.

The administrator who locked it offered this explanation: Archived wiki

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 1: Line 1:
=Note=
 
2.3 was released as [[BZFlag_2.4.0|2.4.0]], the documentation contained here was just a worksheet and does not represent the final list of features released.
 
 
 
==Overview==
 
==Overview==
BZFlag 2.3 was the development version released as 2.4.0. This is to get around the problem that [[BZFlag 2.99]] development has stalled and does not look like it will continue. This is a last ditch effort to get development moving again.
+
BZFlag 2.3 will be a development version that will be released as 2.4.0.0. This is to get around the problem that [[BZFlag 3.0]] development has stalled and does not look like it will continue. This is a last ditch effort to get development moving again.
 
+
==Release==
+
[[BZFlag_2.4.0|2.4.0]] was released on July 3, 2011 and will be maintained as per the [[Development_RoadMap]]
+
  
 
==Goal==
 
==Goal==
Line 14: Line 8:
  
 
==Schedule==
 
==Schedule==
* Move trunk to a v2_99_branch. '''Complete'''
+
* 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.
* Copy v2_0branch to trunk and change protocol number. '''Complete'''
+
* When proposals are in and accepted by consensus, start the 1-month countdown clock.
* Change the version docs to make compatibility be the minor version number. '''Complete'''
+
* Move trunk to a v2_99_branch.
* 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. '''Complete'''
+
* Copy v2_0branch to trunk and change protocol number.
* When proposals are in and accepted by consensus, start the 1-month countdown clock.'''Complete'''
+
* Implement accepted proposals and test.
* Implement accepted proposals and test.'''In progress'''
+
* Change the version docs to make compatibility be the minor version number.
* Document server upgrade process for the many server owners. '''In progress''' ''Thumper by 6/20/2011''
+
* Document server upgrade process for the many server owners.
* If release is not stable by 6/17/2011 revert changes that made it unstable.
+
* After 1 month, revert any changes that have caused unfixed regressions.
* Public beta on 6/20/2011
+
* Do a release candidate before final release?
* Public RC on 6/27/2011
+
* Make trunk into 2.4.0.0 for release.
* Release on 6/30/2011
+
* Tag Trunk to 2_4branch and release.
  
 
==Projects==
 
==Projects==
 
These are the many ideas, both new and old, for changes to BZFlag.
 
These are the many ideas, both new and old, for changes to BZFlag.
 
===Assignments and tracking===
 
Task tracking is managed via a google spread sheet that can be found here.
 
 
https://spreadsheets.google.com/spreadsheet/pub?hl=en&hl=en&key=0Agca59DESlNKdC1CSUtUMUhiSldrOVVPSHcwQUNzOUE&output=html
 
 
Developers with assigned tasks can request edit access to the document on IRC.
 
 
===Timeline===
 
Project must be completed by June 14th 2011 or they will be rolled back and excluded from the release.
 
  
 
===Viable Projects===
 
===Viable Projects===
Line 43: Line 27:
  
 
====Backports====
 
====Backports====
These 2.99 features are suitable for porting to 2.3. Not all items were implemented in 2.4, check [[BZFlag_2.4.0|2.4.0]] release document for final release list.
+
These 2.99 features are suitable for porting to 2.3.
  
* Connection header change (HTTP-style) '''JeffM'''
+
* Connection header change (HTTP-style) ''JeffM''
* New GUI elements '''DTRemenak'''
+
* New GUI elements
* Server-side scoring '''DTRemenak'''
+
* Server-side scoring
* Segmented simulation loop (to prevent wallwalking) '''JeffM'''
+
* Segmented simulation loop (to prevent wallwalking)''JeffM''
* Server-side flag ID and pickup '''Pimpinella'''
+
* Server-side flag ID and pickup
* [[2.3_NewShotGraphics|New shot graphics]] (geolaser/geothief) '''JeffM''' '''Discuss on IRC'''
+
* New shot graphics (geolaser/geothief)''JeffM'' '''Discuss on IRC'''
* HUD markers '''JeffM'''
+
* HUD markers ''JeffM''
* [[2.3_QualityChanges|Removal of low graphics, promotion of experimental to high]]. '''JeffM'''
+
* Removal of low graphics, promotion of experimental to high. ''JeffM''
* Server list from GSoC '''DTRemenak'''
+
* Server list from GSoC
* BZFS API rework '''JeffM'''
+
* BZFS API rework ''JeffM''
* Remove local authentication (the /identify command) '''JeffM'''
+
* Remove local authentication (the /identify command)
* Windows project cleanup '''JeffM'''
+
* Windows project cleanup ''JeffM''
* New make system '''BulletCatcher'''
+
* New make system
* New source docs (authors etc...) '''Constitution'''
+
* New source docs (authors etc...)
* Server-side handicap '''Thumper'''
+
* Server-side handicap
* Guided Missile shot checks '''Pimpinella'''
+
* Guided Missile shot checks
* Stealth fixes for rabbit '''mdskpr'''
+
* Stealth fixes for rabbit
* Asynchronous screenshot compression so client won't freeze up during screenshots '''DTRemenak'''
+
* Asynchronous screenshot compression so client won't freeze up during screenshots
* BZFlag update notification '''DTRemenak'''
+
* BZFlag update notification
* Wings velocity change (additive flap instead of instant upward velocity) '''blast007''' (r14997, r15162, r15832)
+
* Wings velocity change (additive flap instead of instant upward velocity)
* Message protection (ensure network messages are valid) '''A_Meteorite'''
+
* Message protection (ensure network messages are valid)
* Add message types so that actions (/me) are properly implemented '''blast007''' (r19833)
+
* Add message types so that actions (/me) are properly implemented
* New artwork '''JeffM''' [[2.3_NewEffects|Effects Updates]]
+
* New artwork ''JeffM''
* Server option to disable teamkills '''JeffM'''
+
* Server option to disable teamkills ''JeffM''
* OpenFFA '''JeffM'''
+
* OpenFFA ''JeffM''
* Download URL change (to force just images.bzflag.org, not any .org or .bz) '''Constitution'''
+
* Download URL change (to force just images.bzflag.org, not any .org or .bz)
* Remove option to turn off fog '''JeffM'''
+
* Remove option to turn off fog ''JeffM''
* Require OpenGL 1.2 '''JeffM'''
+
* Require OpenGL 1.2 ''JeffM''
* Only allow a single end shot credit for holding the shield flag '''Thumper'''
+
* Only allow a single end shot credit for holding the shield flag
* Only players with POLL permission are eligible to take part in a vote '''Thumper'''
+
* Only players with POLL permission are eligible to take part in a vote
* Add the /serverdebug command '''Thumper'''
+
* Add the /serverdebug command
* bzfs: Report errors to stderr instead of stdout '''Thumper'''
+
* bzfs: Add -utc switch to output log messages in UTC instead of localtime '''Thumper'''
+
* bzfs: Fix timestamp buffer size so -ts micros output fits '''Thumper'''
+
* Joystick input fixes/enhancements '''DTRemenak'''
+
* Remove -geometry and make -window take a size '''JeffM'''
+
* bzfs: Allow -time to have an ending time '''blast007'''
+
  
 
====New Changes====
 
====New Changes====
* Round Robin for services '''JeffM'''
+
* Round Robin for services
 
* Fix the protocol bug that version [[BZFlag 2.0.16|2.0.16]] was a band-aid for
 
* Fix the protocol bug that version [[BZFlag 2.0.16|2.0.16]] was a band-aid for
* Facilitate moving global services (e.g., my.bzflag.org) to new hardware, if any changes will help '''JeffM''' '''Blast007''' '''JoeVano'''
+
* Facilitate moving global services (e.g., my.bzflag.org) to new hardware, if any changes will help ''JeffM'' ''Blast007'' ''JoeVano''
* Import client customization settings from the 2.0 config.cfg file to the 2.4 version
+
* Implement new version numbering system into code. (/src/date/buildDate.cxx and DEVINFO at least, there might be more places where it is needed)
+
  
 
===To Evaluate===
 
===To Evaluate===
Line 94: Line 70:
  
 
====Backports====
 
====Backports====
* Map changes '''mdskpr'''
+
* Map changes
* HTTP plugins '''JeffM'''
+
* HTTP plugins
* New API events '''JeffM'''
+
* New API events ''JeffM''
* Custom flag system '''DTRemenak'''
+
* BZFSCron
* BZFSCron '''Thumper'''
+
* Server Side Players ''JeffM''
* Server Side Players '''JeffM'''
+
* Bug fixes not in notes
* Bug fixes not in notes '''Thumper'''
+
* New flags
* Hunter as proper team '''mdskpr (grabbed by DTRemenak)'''
+
* Rabbit as proper team
* bzfs -publickey '''trepan'''
+
* push stats as default
+
  
 
====New Changes====
 
====New Changes====
* Countdown/reload timer position fix for when showCoordinates is enabled '''mdskpr'''
+
* Countdown/reload timer position fix for when showCoordinates is enabled
* SVN props cleanup '''BulletCatcher'''
+
* SVN props cleanup
* Display BZBB rank images in game. '''JeffM'''
+
* Display BZBB rank images in game. ''JeffM''
  
 
===Exclusions===
 
===Exclusions===
 
These items should not be done or backported at this time due to stability issues or the large effort required. These are generally the blocking items preventing 3.0's current release.
 
These items should not be done or backported at this time due to stability issues or the large effort required. These are generally the blocking items preventing 3.0's current release.
  
* New flags
 
 
* Network buffering
 
* Network buffering
 +
* Lua
 
* Lag compensation (needs a lot more testing)
 
* Lag compensation (needs a lot more testing)
 
* Acceleration changes
 
* Acceleration changes
Line 120: Line 94:
 
* New Translations (requires the new font system)
 
* New Translations (requires the new font system)
 
* Map geometry changes (requires flag zap zone support or breaks existing servers)
 
* Map geometry changes (requires flag zap zone support or breaks existing servers)
* Website changes.
 
 
==Known Issues==
 
===Empty Flag Types===
 
When you start BZFS with +f good{2} the server will generate 8 "empty" flag IDs in addition to all normal good flags (no flag type.)
 
This can be seen by doing '/flag show'. You can also '/flag give' the empty flag types, although all it seems to do is say "user: grabbed flag " in chat and make the flag pick-up noise - it doesn't actually give you a flag.
 
 
[[Category:Versions]]
 

Please note that all contributions to BZFlagWiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see BZFlagWiki:Copyrights for details). Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel | Editing help (opens in new window)