> 2009/10/9 Marko Lindqvist <cazf...@gmail.com>: >> 2009/10/8 Matthias Pfafferodt <matthias.pfaffer...@mapfa.de>: >>> OK; so is there a possibility for this to go into 2.2.0? >>> >> >> Â Main reason to very long release cycles is that we want to fit too >> many new features to each release instead of "release early, release >> often". > > I know it can be frustrating that new features you are writing now are > postponed to 2.3 - it may take years for them to appear to end user > (unless we success in shortening release cycles). I have written some > features immediately after S2_1 branching (3.5 years ago) and first > time they will be released is when we finally release 2.2.0. But > trying to fit features in earlier release just to avoid this long wait > only makes things worse. Sorry.
I understand and due to the fact that I use trunk to play games at home (single player) this is not a problem. > > At the moment I don't have much time, but this seems something which > > should be done. I think 2.3.0 (or 2.2.1?) will have this ;-) > > There's a lot of time before 2.3.0 will be released - most likely too > much time (I really hate it how long our release cycles take) 2.2.1 > will be bugfix release from S2_2 branch. After this I had to ask ;-) > > > - ML > > _______________________________________________ > Freeciv-dev mailing list > Freeciv-dev@gna.org > https://mail.gna.org/listinfo/freeciv-dev > -- Matthias Pfafferodt - http://www.mapfa.de Matthias.Pfafferodt <at> mapfa.de _______________________________________________ Freeciv-dev mailing list Freeciv-dev@gna.org https://mail.gna.org/listinfo/freeciv-dev
