Possible 4.3.0 blocker in the Konsole KPart?

Maciej Mrozowski reavertm at wp.pl
Wed Aug 5 23:10:04 CEST 2009

On Wednesday 05 of August 2009 08:17:03 John Tapsell wrote:

> Agreed.  I can't get the hang of svn backporting, and so I simply never do
> it.

I'm a bit scared hearing this..
Maybe because being packager I usually rely on developers to decide about the 
way product is supposed to look like (not to mention it's far easier this 
way...) - and if backporting was not popular among developers (fortunately 
it's usually not the case), then trunk would always feel "broken" (hey, it's 
supposed to be that way :) - and stable branch would be 
underdeveloped/abandoned/forgotten - this way users would never really get 
polished release.
That being said I really think that migrating to better SCM is crucial and 
should be done as soon as possible.
Aaron mentioned possibility of working in stable and then forward porting. 
While it may certainly bring more focus on bugfixes, it may cause features 
being introduced at smaller pace - it's up to you to decide what's most 
appropriate at this point of KDE release timeframe.
In any way - like Aaron noted, SVN doesn't help here (unless you forget about 
branches and go back to continuous in-trunk development - but that would 
expose patch releases to regressions so it's dead end).

> Once we have git, I'd like to see this issue revisited.  I would
> prefer that KDE got a reputation of "releases when ready".  Just start
> skipping the release that we currently call ".0".

That won't solve anything. x.y.0 releases are important - even just for their 
PR value  - even if they're half-baked - it's just up to distributions to pick 
the one that satisfies it best.
Reputation of high quality can be achieved without skipping releases. It 
"just" needs:
- regarding developers - the will to write reliable, bullet-proof code and 
backport it if needed
- for developers - tools that help and don't disturb (currently lack of 
thereof can be only compensated by even greater developers' will)
- better distro<->developers cooperation, distributions provide free testers 
after all (btw, how many of you use stable branch daily?) Are there currently 
any serious problems with such cooperation?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/release-team/attachments/20090805/97691467/attachment.sig 

More information about the release-team mailing list