TODO for next release

[softcoder]

What needs to be done before we make a new release?

Changelog

v3.7.0
- bugfixes reported in the bugs forum since 3.6.0.3
- first person view allows you to follow a selected unit. Select one unit anf press f4 to enable (deselect anf f4 to disable).
- cell markers allow players to create markers anywhere on the map and associate a note with them. All team players see the markers.
- quick sonar signal to tell team players where the action is happening
- admin player can disconnect other network players in game
- saving / loading games.
- when placing a new unit, we display a 'ghosted' model while units walk to the build location to show the space it will occupy
- video playback support (using libvlc)
- network multi-player scenarios
- campaign scenarios
- play a sound when player mentions your name in chat mode
- more game data validation for commandline modders, see --help for more info
- many new lua commands for scenario modders
- enhanced AI management (logging and modding) and added more intellegence to decsions
- enhanced unicode support for non-ascii characters
- customizable unit, resource and upgrade language files
- tilesets support animated models
- scenario factions may now be 'neutral', meaning not on any players team.
- new command action mouse cursors
- resources are selectable showing info about the resource
- particle colors are now affected by the time of day
- new game hints are displayed while loading a new game
- linked faction support (and new techtree MagiTech for classic Glest play)

[tomreyn]

An incomplete list (and also an attempt at documenting the release process - because I think we really need to document it - I keep forgetting stuff every time):

• Bug fixes: Look into / comment on open bugs (that's the ones where the subject line starts without any [tag])
• Optionally: set up new build infrastructure, optionally controlled by Jenkins
• Code cleanup
• Define deadline for localization changes
• Request, re-request, test and commit translations
• Test games on headless servers, including mod download, everyone running a given SVN snapshot. Requires a universal Linux build, made from the same SVN revision which the latest Windows nightly was made from, and an announcement on mailing lists + identi.ca incl. instructions and timeanddate.com link
• Test map editor and model viewer on all platforms
• Update / rewrite build instructions (deprecate VC 2008, recommend scripted builds over VC GUI)
• Update documentation: in-release and on the wiki
• Update changelog
• Build installers, prepare data + source code packages; optionally: GPG-sign everything
• Test installers
• Test building from source code package
• Test non-installer archives
• Upload everything
• Update website: news, downloads, techtree documentation
• Update in-game / masterserver announcement + version info
• Upgrade headless servers, where possible
• Send release announcement
• Spread the word

Softcoder, Titi: You are welcome to edit this post to complete the list.

[titi]

- lua commands to set a flag
- other flag image for markers maybe
- ( maybe include an intro movie of real gameplay using the new possibilities of a the vlclib  )

I vote to call next release 3.7.0, so next beta should be called 3.7.0_beta1 .

[tomreyn]

In addition to untagged bugs fixed, I'd really like the following features implemented for next release, if possible:

• [done] Port numbers in servers.ini
• Disable loading of resources (videos, network scenarios, other game mods) from remote resources which are not under our management or otherwise known to be safe
• Disable network scenarios (until there is a secure implementation)

It's hard to tell how much work it would involve to implement these, so please don't spoend too much time if it would take that.

I'll probably extend this post over time, so please re-check later.

[tomreyn]

Regarding what needs to be done for a beta, Titi said yesterday that it would be nice to take another hard look at performance (but since it's a beta, this could be postponed, too). Regarding performance, he's mostly thinking about whether or not to enable the (currently disabled) cache we used to have in 3.6.0.3.

Personally I'd like all non-[tagged] bugs to be investigated and commented on (if only "not enough info, won't fix"), but this, too, could be postponed. It could be nice to create the betas on the new build infrastructure, though (to setup and test run the automation involved), also as a test run for (possibly) fully automated builds for the stable release, but this would most likely take more time than doing it the classical way.

[softcoder]

Added some security around lua scripts in general. Its not perfect but it handles most problems.