3 Jan 16:35
3 Jan 17:27
Akonadi 1.1.0 Released.
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, Toma
3 Jan 17:33
tags/kdesupport-for-4.2
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 probably commit some KDE 4.2.x incompatible changes in kdesupport trunk as soon as KDE 4.2 is branched. Request to all kdesupport maintainers: add the version of your software into that tag soon please. Toma
3 Jan 17:57
announcements (was: Re: tags/kdesupport-for-4.2)
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 (which would be KDE 4.3.0). > > At least Akonadi will probably commit some KDE 4.2.x incompatible changes > in kdesupport trunk as soon as KDE 4.2 is branched. > > Request to all kdesupport maintainers: add the version of your software > into that tag soon please. Can we have an announcement for this on kde-cvs-announce once this is mandatory? Same applies for when the freeze is over and all other milestones as wellWe've had a thread about this quite some time ago, but I'd like to stress this again. Thanks, Dominik
3 Jan 18:22
The road to 4.3
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 on when we see some massive code changes in 4.3, which warrants an extra release. Let me know when the schedule is wrong for some reason. http://techbase.kde.org/Schedules/KDE4/4.3_Release_Schedule I'ld like to announce this schedule to k-c-d by the end of next week. Toma
3 Jan 20:14
Re: The road to 4.3
On Saturday 03 January 2009, Tom Albers wrote: > 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. sounds great. > I've cancelled the Alfa release, as it brings almost no feedback. We can > add it to the schedule later on when we see some massive code changes in > 4.3, which warrants an extra release. agreed > http://techbase.kde.org/Schedules/KDE4/4.3_Release_Schedule question for developers, perhaps: how did they find the 6 weeks of beta and bug fixing this time around? enough time, not enough time, too long? how about the number of betas made? it would be great if we could get some feedback from developers (e.g. a small online survey) regarding things like this. after 4 months of feature dev, spending 1.5 months not doing feature dev (counting from the start of beta1) was a bit of a long singular chunk, but had value.(Continue reading)
3 Jan 20:21
Re: Branching KDE 4.2
On Saturday 03 January 2009 09:35:17 am Tom Albers wrote: > 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 Correct. I, for one, can't wait until trunk reopens. :) -- -- Matt
3 Jan 20:52
Re: The road to 4.3
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 and releaseing. I considered reducing the time in my previous mails, but it requires a faster tagging to release period. So without changing the week between tag and release it goes like this for a 2 week cycle: week 1 wednesday: tagging b1 week 2 wednesday: releasing b1 week 3 wednesday: tagging b2 week 4 wednesday: releasing b2 Which effectively means that you have 1 week to get the bugs and fix them, though receiving bugs during week 3 is not that bad, new fixes can not longer be added to b2. So, to work with a 2 weeks beta cycle, we need to reduce the period between tag and release: Week 1 monday: tag b1 Week 1 wednesday: release b1 Week 3 wednesday: tag b2 Week 3 friday: release b2 Which effectively means that the period has increased to 2 weeks, which is a lot better imho. Toma
3 Jan 21:00
Re: The road to 4.3
On Saturday 03 January 2009, Tom Albers wrote: > So, to work with a 2 weeks beta cycle, we need to reduce the period between > tag and release: Week 1 monday: tag b1 > Week 1 wednesday: release b1 > Week 3 wednesday: tag b2 > Week 3 friday: release b2 > > Which effectively means that the period has increased to 2 weeks, which is > a lot better imho. if this is possible and realistic to achieve without causing the release team to tear their hair out and run screaming, it would be wonderful. -- -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Software
4 Jan 13:09
Re: tags/kdesupport-for-4.2
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 (which would be KDE 4.3.0).
>
> At least Akonadi will probably commit some KDE 4.2.x incompatible changes
> in kdesupport trunk as soon as KDE 4.2 is branched.
>
> Request to all kdesupport maintainers: add the version of your software
> into that tag soon please.
>
> Toma
Another request to all kdesupport maintainers:
KDE 4.2 will require CMake 2.6.2.
The different projects in kdesupport require different versions of CMake:
CMake 2.4.5: qca
kdewin-installer
akonadi
automoc
eigen2/bench/btl/
CMake 2.6.2: kdewin32
All others require CMake 2.6.0.
(Continue reading)
RSS Feed