KDE 3.5.8

[Andreas Pakulat]

On 01.10.07 08:36:28, Stephan Kulow wrote:
> Am Montag 01 Oktober 2007 schrieb Andreas Pakulat:
> > On 26.09.07 13:50:51, Andreas Pakulat wrote:
> > > On 21.09.07 10:02:43, Stephan Kulow wrote:
> > > > Hi!
> > > >
> > > > It's been a while since KDE 3.5.7 (released may 22nd) and a lot has
> > > > changed in the 3.5 branch since then, so I would like to release
> > > > another service pack.
> > > >
> > > > As the translators requested some clean up time, I suggest we go with
> > > > October 7th as tagging date and release on 15th.
> > > >
> > > > Any objections? If not, I let everyone know :)
> > >
> > > About KDevelop :)
> > >
> > > We recently moved to a branch (please no flames anymore, got enough of
> > > that already) and some of us developers would like to merge that branch
> > > back into KDE/3.5 before this release. The thing is, that
> > >
> > > a) that branch has new strings (I already changed scripty to update from
> > > the branch instead of KDE/3.5 a few weeks ago)
> > > b) it has new features
> > >
> > > I know 3.5 is in full freeze, thats why I'm asking wether we are allowed
> > > to move back at all.
> > >
> > > If not, please don't release the kdevelop module from KDE/3.5 when
> > > releasing KDE 3.5.8. We will do a release of KDevelop 3.5.0 at the time
> > > of the KDE release ourselves in that case. (Should kdevelop 3.4.1 be
> > > removed from KDE/3.5 in that case?)
> >
> > Would somebody please give us (the kdevelop team) at least any response?
> > (no I will not do the move unless it is approved, but still its kinda
> > rude to get no answer whatsoever)
> >
> Oops, I overlooked the mail somehow.  I was aware of the issue though. So the 
> thing is: if you already changed scripty, then merging back is the safer 
> variant. Otherwise 3.5.8's kde-i18n might create a more untranslated kdevelop
> than with the branch.
>
> I wonder why you guys don't ask forehand.

We did ask to get a freeze exception, but we got no reply whatsoever :(

> Now all I could do is remove kdevelop from kde-i18n and 3.5.8
> completely ;(
> 
> But backmerge, I don't care. The idea in freezing KDE 3.5 was to keep people 
> on KDE4 development, if it doesn't work for kdevelop and the development team 
> is using dirty tricks to circumvent the freeze, I can't help.

Ok, I'll merge back the branch then. 

Note that we're not _actively_ working on KDevelop3.x anymore, at least
not as the few of us work on KDevelop4. Howver its still a long road
until 4.0 is released and there are certain "bugs" that need a small
feature here or there (and one of us is payed to improve a certain
language support, which of course makes sense to share with the
community)

Thanks for the answer.

Andreas

-- 
Chess tonight.