[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: KDE3 maintenance
From:       Pau Garcia i Quiles <pgquiles () elpauer ! org>
Date:       2009-11-19 11:21:24
Message-ID: 3af572ac0911190321u48d937ccu9a9bf18d19e30a96 () mail ! gmail ! com
[Download RAW message or body]

On Thu, Nov 19, 2009 at 11:20 AM, Tom Albers <toma@kde.org> wrote:
 commits, apart from the fact that I think no-one will be very excited
to do that for such old code, it takes away time from the normal
hacking someone is doing.
> 
> Let alone if you would actually test the patches that goes in. For many \
> of us that would mean setting up a KDE3 development environment from \
> scratch. I don't think we can deal with that, so I don't think we can put \
> our 'ok' on it, so I think they should not be committed.

I disagree.

Given that we have tags for 3.5.9, 3.5.10, etc, I propose that new
commits for KDE3 go to /branches/KDE3 and we DO NOT release 3.5.11.
New versions should be packaged by distributions as
"3.5.10+svn1051246" (or whatever the latest revision for that
"snapshot" of KDE3 is).

I think this achieves the best of both worlds: we have all the KDE3
code in our repository but as we have not tagged or released that
version, we are not giving an OK.


-- 
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)
 
> > Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to \
> > unsubscribe <<


[prev in list] [next in list] [prev in thread] [next in thread]