(clean) |
Mark Ziegler (Talk | contribs) |
||
| Line 1: | Line 1: | ||
The major change in KDE 3.0 will be the switch to Qt 3, as well as new features and bugfixes that involve bigger changes or require breaking binary compatibility. The plan is to make KDE ready for a long period of binary compatible releases. | The major change in KDE 3.0 will be the switch to Qt 3, as well as new features and bugfixes that involve bigger changes or require breaking binary compatibility. The plan is to make KDE ready for a long period of binary compatible releases. | ||
| − | The list of planned features can be found in a separate document. | + | The list of planned features can be found in a [http://developer.kde.org/development-versions/kde-3.0-features.html separate document]. |
All dates given here are subject to revision, but we will try our best to stick to them if possible. | All dates given here are subject to revision, but we will try our best to stick to them if possible. | ||
The major change in KDE 3.0 will be the switch to Qt 3, as well as new features and bugfixes that involve bigger changes or require breaking binary compatibility. The plan is to make KDE ready for a long period of binary compatible releases. The list of planned features can be found in a separate document. All dates given here are subject to revision, but we will try our best to stick to them if possible.
Dirk Mueller is acting as release coordinator for the 3.0 releases.
The HEAD branch should be made ready to compile and work flawlessly with the current Qt 3.x beta / release version.
The HEAD branch is tagged as developer-release / alpha named KDE_2_9_RELEASE and tarballs are made.
The HEAD branch is frozen for feature commits that are not listed in the planned-feature document. Only bugfixes and the listed feature-commits are to be committed. Still, binary compatibility is not required, i18n string changes are allowed.
KDE 3.0 Beta 1 is tagged and tarballs are made for testing. The HEAD branch is frozen except for urgent bug- and compile fixes. The rest of the week is spent testing the tarballs, packaging and writing the announcement and changelog.
Beta 1 is announced. The HEAD branch is frozen except for bugfixes and for the eventually outstanding feature commits listed in the planned-feature document. i18n string changes are to be kept at a minimum to allow translation teams that have to start from scratch to get a certain amount of work done.
3.0 Beta 2 is tagged and tarballs are made for testing. The HEAD branch is frozen for release. i18n is completeley frozen for string changes by developers. Any nontrivial patches to CVS has to be approved by at least another developer. Announcement a week later.
3.0 Beta2 is released to the public.
3.0 RC1 tarballs are made and uploaded for testing.
3.0 RC2 tarballs are made and uploaded for testing.
3.0 RC3 tarballs are made and uploaded, which incorporate the CVS changes since RC2 tarballs. Remaining showstoppers are identified. The tarballs are made available to the packagers and put up on ftp. Binary packages will be publically announced together with the source tarballs as soon as they become available.
Manually selected changes since the RC3 tarballs are integrated into the proposed final tarballs, labeled RC4. A check of the showstopper list will decide if these tarballs are final. In this case, they're made available to the packagers and roughly a week later announced to the public. If not, the schedule is delayed by another week.
The final tarballs are made available to the packagers. The remaining week is used to prepare the changelog and the announcement.
The final tarballs are made available on ftp.kde.org and the release is announced.
the KDE_3_0_BRANCH is tagged as KDE_3_0_1_RELEASE and tarballs are made for the packagers. Announcement roughly a week later.
The tarballs and the binary packages are announced to the public after some delays.
The KDE_3_0_BRANCH is tagged as KDE_3_0_2_RELEASE and tarballs are made for the packagers. Announcement roughly a week later.
The KDE_3_0_BRANCH is tagged as KDE_3_0_3_RELEASE and tarballs are made for the packagers. Announcement roughly a week later.
The KDE_3_0_BRANCH is tagged as KDE_3_0_4_RELEASE and tarballs are made for the packagers. Announcement roughly a week later.