[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-commits
Subject: www/sites/developer/development-versions
From: Allen Winter <winter () kde ! org>
Date: 2007-04-04 14:33:44
Message-ID: 1175697224.732743.1239.nullmailer () svn ! kde ! org
[Download RAW message or body]
SVN commit 650425 by winterz:
move to techbase
M +1 -63 kde-4.0-release-plan.html
--- trunk/www/sites/developer/development-versions/kde-4.0-release-plan.html \
#650424:650425 @@ -3,70 +3,8 @@
$page_title = "KDE 4.0 Release Plan";
include 'header.inc';
?>
- <p>The following is the outline for our KDE 4.0 release schedule.</p>
+ <p>This page has moved to <a \
href="http://techbase.kde.org/Schedules/KDE4/4.0_Release_Schedule">http://techbase.kde.org/Schedules/KDE4/4.0_Release_Schedule</a>.
- <p>The "main to-do list" can be found in a <a \
href="kde-4.0-todo-list.html">separate document</a>.</p>
- <p>All dates given here are subject to revision, but we will try our best to \
stick to them if possible.</p>
-
- <p>The KDE Technical Working Group is acting as release coordinator for the 4.0 \
releases.</p>
-
- <h2>KDE 4.0 Technical Preview 1</h2>
-
- <h3><b>October ... 2006: Technical Preview 1</b></h3>
- Targetted date for first technical preview, mostly a developer release.
-
- The kdelibs API will remain as stable as possible after that, so that \
application developers
- (in particular those not having their code in the KDE SVN) can start porting \
towards a stable kdelibs API.
- Of course the applications in the KDE SVN will have been ported all along, and \
it will
- possible to alpha-test them at this stage.
-
-
-
-
- <h2><b>Frequently Asked Questions</b></h2>
-
- <h4>What's the deal with that feature-plan?</h4>
- There isn't an official feature plan yet. The current feature list is on <a \
href="http://wiki.kde.org/KDE+4+Goals">the KDE wiki</a>.
-
- <h4>So, when will KDE 4.0 final be out?</h4>
- This isn't decided yet.
-
-<!-- <p>In the past, there were a lot of complaints about a rather long "freeze \
period", so this is an attempt to address this issue. Basically the idea is that you \
add an entry about what feature you want to finish in the 3.5 timeframe and mark it \
as done when you completed it. This helps me to get an overview about the outstanding \
changes and in return allows you to work on the missing parts even in the "freeze \
period".</p>
-
- <p>The feature-plan is open for commits till August 1st 2005.<u>Later \
additions</u> require reviewal first. I will try to respect outstanding entries in \
the release schedule.</p>
-
- <p>Please understand that although this gives you greater freedom over SVN, it \
also requires more discipline in making sure that your additions don't have unwanted \
side effects.-->
- <!--
- <h4>Which packages are included?</h4>
- <p>The current list of packages that will be in the 3.5 release is:
- <pre>
-
- arts
- kdelibs
- kdebase
- kdenetwork
- kdegraphics
- kdeadmin
- kdeaddons
- kdeartwork
- kdemultimedia
- kdegames
- kdeutils
- kdetoys
- kdepim
- kdesdk
- kdebindings
- kdevelop
- kdewebdev
- </p>
- -->
- </p>
- <hr size="2" align="center" noshade="noshade" />
-
- <center>
- <font size="-1">Last update: 16 February 2006, <a \
href="mailto:faure@kde.org">David Faure</a></font>
- </center>
-
<?php include ("footer.inc"); ?>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic