Road map - order of next releases

[tomangelo]

Our current order with releasing Gold looks like "We'll put this feature, and this, and fix 5 bugs, after 2-3 months we'll put this feature and another 15 bugfixes and maybe after 6 months after last update we'll release new version of the game. Meanwhile we created a new branch". I think we could think about some kind of project roadmap, so when we release (for example) 0.1.6, we should have closed list of issues for 0.1.7 (except for very important situations, like 'Preparing Gold to ASCC (Another Super Cool Contest) 2017'), think what we'll add to 0.1.8 (like "New bots, maps, rewriting physics code"). When we'll finish Release 0.1.7, we should have closed list of issues for 0.1.8 (except for very important situations, like 'Preparing Gold to YAMCC (Yet Another Mega Cool Contest) 2017'), think what we'll add to 0.1.9 (like "New exercises, rewriting to SDL 2") and so on.
I don't know what do you thinking about this idea, but I think we should really do something with current situation.
(Referring to first paragraph: I know that not everyone have a time to develop the game, and there's nothing we can do, I've mean that we don't even know what we'll add to next release).

[krzys_h]

This is how our plan for future releases looks like right now:

• 0.1.5
  • support for %lvl% everywhere
    
  • use PHYSFS for saving
    
  • bugfixes to gameplay and controls
    
• 0.1.6
  • bugfixes to 3D graphics
    
• 0.1.7
  • new model format
    
  • move animations out of source code
    
• 0.2.0
  • rewrite CBot engine
    
• 0.3.0
  • rewrite UI to CEGUI
    
  • UI bugfixes
    

Bugfixes for game-breaking bugs are ussualy assigned to next release (0.1.5 right now).
This is mostly how issues are currently assigned to milestones on GitHub: https://github.com/colobot/colobot/milestones

I think our current plan for releases should stay as it is, and that we should keep fixing any major bugs before release. At least, that's what I'm trying to do most of the time.