I'd like to propose to have a policy that reduces period between stable releases. In our context, time between 2.8.4 and 2.9.0 shall be minimal.
That can be achieved by releasing more 2.8.x versions if really needed or by releasing 2.9.0 earlier. Justification: in a not so intensive development I never know when an important bug and fix pops up. I'd like to reduce "time-to-market". On 3 April 2014 16:29, Cyrille Berger <cber...@cberger.net> wrote: > Hi, > > I have updated the release plan for maintenance release for 2.8: > > http://community.kde.org/Calligra/Schedules/2.8/Release_Plan > > 2.8.3 and 2.8.4 might be readjusted depending on the rate of bug fixing, > and further releases might be added with the same consideration. > > So what about 2.9 ? I could suggest branching early august and a release > in September/October ? Or do you want a release earlier/later ? > > -- > Cyrille Berger Skott > _______________________________________________ > calligra-devel mailing list > calligra-devel@kde.org > https://mail.kde.org/mailman/listinfo/calligra-devel > -- regards / pozdrawiam, Jaroslaw Staniek Kexi & Calligra & KDE | http://calligra.org/kexi | http://kde.org Qt for Tizen | http://qt-project.org/wiki/Tizen Qt Certified Specialist | http://www.linkedin.com/in/jstaniek
_______________________________________________ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
