(feature plans and releases/schedules are tightly coupled. So let's put the feature plans into Schedules/* as well.) |
m (link to more information about release schedules) |
||
| Line 2: | Line 2: | ||
During development, the KDE project sets goals in features and dates for upcoming releases. This way, the team knows when it would be a good time to add a new feature or when it's time to | During development, the KDE project sets goals in features and dates for upcoming releases. This way, the team knows when it would be a good time to add a new feature or when it's time to | ||
| − | focus on cleaning up any bugs in preparation for a release. Any plans are tentative schedules and the final dates are generally decided on the kde-core-devel mailing list. | + | focus on cleaning up any bugs in preparation for a release. Any plans are tentative schedules and the final dates are generally decided on the kde-core-devel mailing list. |
| + | |||
| + | Learn more about [[/Release Schedules|release schedules]]. | ||
== KDE == | == KDE == | ||
During development, the KDE project sets goals in features and dates for upcoming releases. This way, the team knows when it would be a good time to add a new feature or when it's time to
focus on cleaning up any bugs in preparation for a release. Any plans are tentative schedules and the final dates are generally decided on the kde-core-devel mailing list.
Learn more about release schedules.
KDE TechBase 