Hi,
If I remember correctly usually the branching happens at release candidate
fase, does that mean that later this week trunk becomes 4.3 and open for
features again?
Toma___
release-team mailing list
release-team@kde.org
Hi,
In preparation of the KDE 4.2.0 release, we have released Akonadi 1.1.0 now.
So, to be clear:
KDE 4.1.x must use Akonadi 1.0.x ( 0 for now )
KDE 4.2.x (incl. release candidates) must use Akonadi 1.1.x ( 0 for now )
Download it from: http://download.akonadi-project.org/
Best,
Hi,
In preparation of the release of 4.2.0, I've created the
tags/kdesupport-for-4.2. This tag of kdesupport should be used when you compile
the 4.2 branch in the future. Trunk's version of kdesupport should be used to
compile KDE trunk (which would be KDE 4.3.0).
At least Akonadi will
Hi,
On Saturday 03 January 2009, Tom Albers wrote:
Hi,
In preparation of the release of 4.2.0, I've created the
tags/kdesupport-for-4.2. This tag of kdesupport should be used when you
compile the 4.2 branch in the future. Trunk's version of kdesupport
should be used to compile KDE trunk
Hi,
I've put up a schedule for 4.3.
As we have Akademy on 3rd of July, I've planned to have released RC1 by that
date, as we branch at that stage, trunk is open for features during Akademy.
I've cancelled the Alfa release, as it brings almost no feedback. We can add it
to the schedule later
Op Saturday 03 January 2009 20:14 schreef u:
it would be great if we could do a beta (or whatever you want to call it)
every two weeks to allow for a faster test-fix-test cycle during the
stabilization (non-feature-dev) period of the cycle.
Please note that there is a week between tagging
