(→KDE4) |
(→KDE4: add placeholder for 4.2 upstream issues and compilation requirements) |
||
| Line 14: | Line 14: | ||
** [[Schedules/KDE4/4.2 Release Goals|Release Goals]] | ** [[Schedules/KDE4/4.2 Release Goals|Release Goals]] | ||
** [[Schedules/KDE4/4.2 Feature Plan|Feature Plan]] | ** [[Schedules/KDE4/4.2 Feature Plan|Feature Plan]] | ||
| + | ** [[Schedules/KDE4/4.2 Upstream Issues|Release Critical Upstream Issues]] | ||
| + | ** [[Schedules/KDE4/4.2 Requirements|Compilation Requirements]] | ||
*'''KDE 4.1''' | *'''KDE 4.1''' | ||
| Line 20: | Line 22: | ||
** [[Schedules/KDE4/4.1 Feature Plan|Feature Plan]] | ** [[Schedules/KDE4/4.1 Feature Plan|Feature Plan]] | ||
** [[Schedules/Is KDE 4.1 for you?|Is KDE 4.1 for you?]] | ** [[Schedules/Is KDE 4.1 for you?|Is KDE 4.1 for you?]] | ||
| − | |||
*'''KDE 4.0''' | *'''KDE 4.0''' | ||
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 