The KDE Release Team has a list with things that need to happen before we can get KDE 4.0
\n out of the door. I feel it’s a good idea to share this with the wider community as much as
\n possible. We need to get our noses aligned and head for 4.0. This will be a huge effort, but
\n on the way to the finish line for 4.0, we’ll need to focus on the following things:<\/p>\n
The Beta Cycle will continue until these critical components are determined
\n to be functional (i.e. the “Minimum Requirements”). Our hero David Faure put it very nicely:<\/p>\n
Let’s fix the damn code before we think about betas and parties :-)<\/p><\/blockquote>\n
\n The Release Team is contacting people in charge of those components to give more detailed
\n We shoud encourage people to work on those priority items instead of other things which can
\n information about the status and what to expect.<\/p>\n
\n be deferred into the 4.0 cycle. Getting 4.0 out of the door will be heavy lifting, now is
\n time to show that we can function as one<\/strong> community with one<\/strong>
\n shared goal. So if you want to see KDE 4.0 released (and I boldly assume we all do), help with
\n fixing the bits above.
\n <\/p>\n","protected":false},"excerpt":{"rendered":"The KDE Release Team has a list with things that need to happen before we can get KDE 4.0 out of the door. I feel it’s a good idea to share this with the wider community as much as possible. We need to get our noses aligned and head for 4.0. This will be a… Continue reading Development Priorities<\/span>