Hi,
There was a discussion on IRC about it a little while ago about the release
schedule, one of the conclusion was that soft-freeze was not needed anymore.
But some people thought that the freezing time would be too long, so here is
an alternative schedule.
August 31th -> soft freeze, no more features in master, features in
master are restricted to features discussed
before hand and that can justify an
September 7th -> beta1 is tagged
September 14th -> beta1 is released
September 30th -> beta2 is tagged
October 5th -> beta2 is released
October 12th -> String freeze, any changes to a string in futurestable
needs to be discussed with the translation
teams (except for typo that are bug fix and you
only need to ping the translation teams)
It also means no new features can be added
October 21th -> beta3 is tagged
October 26th -> beta3 is released, master is branched into
"futurestable", and master get open again for
new features, and "futurestable" is the branch
were bug fixes for 2.4 need to go
November 18th -> RC1 is tagged, "futurestable" is closed, and merged in
"stable"
November 23th -> RC1 is released
It is worthwhile to remember that while new features are allowed in the beta
cycle, it should be the exception, not the norm.
So what do you think ? Is it better with the feature exception, or do most
people prefers no feature exception ?
--
Cyrille Berger Skott
_______________________________________________
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel
