Moving 3.5 development into branches/KDE/3.5

[Matt Rogers]

On Monday 30 May 2005 02:21 pm, Stephan Kulow wrote:
> Am Montag 30 Mai 2005 15:49 schrieb Matt Rogers:
> > IMHO, this doesn't sound any different than what we're doing now with the
> > kde4 work branch. Why make a switch at all?
>
> This is a change of policy and was the initial goal. The kde4 work branch
> was just temporary. The main difference to the current situation is:
>
> * KDE4 is the main target, KDE 3.5 development is defined as backport
>
> Greetings, Stephan

Then I have to ask why are we changing the current policy? From my POV, I see 
no benefits, only problems. The biggest problem being that KDE 3.5 then 
becomes seen as more of a red-headed step child when it could possibly be the 
most important KDE release (since it will have the longest lifetime) until 
KDE 4 comes out.

we're also going to have to educate people on how to actually get a KDE that 
they can use, since many anonymous svn users will pull trunk blindly. let's 
also not forget the amount of people in irc channels and sending emails 
saying "KDE from trunk doesn't work!" or "KDE from trunk is broken!" Yes, 
they're taking the risk of running a development version, but we still have 
to be wary of this because people will start making judgements about all of 
KDE based on what they get from their svn compiles.

/me flips two cents into the fountain

Matt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20050530/b2c8ea6c/attachment.sig>