Re: KDE 3.5.8

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?)

Re: Questions About the New Schedule

On Saturday, 8. September 2007, Albert Astals Cid wrote:

> > 5)  Should language bindings be part of the development platform?
> > Richard Dale says "Python and Ruby in good shape by late October, and
> > possibly C# too."
>
> If Richard says he can do it, i say we can try it 

Thats not enough. somebody has at least to be able to confirm that the 
bindings *compile*. right now, kdebindings does not compile, and after I 
spent an hour or so looking, I'm sure that it can not compile for anyone at 
all, given the fundamental bugs in the build system. 

it is my understanding that Richard uses a completely different build system 
to maintain the bindings, at least thats what he used to do in KDE3 times. 
There has to be at least somebody who maintains the official build system, 
and that person has to be != me. 

Greetings,
Dirk

apaku@...: Translations for KDevelop 3.5]

On Saturday, 8. September 2007, Andreas Pakulat wrote:

> Unfortunately I picked the wrong adress for the release-ml when I first
> sent this. So I'm forwarding the mail and patch now. Please have a look
> and if you reply include kdevelop-devel so the other kdevelop hackers
> will see the answers as well.

One issue I see with this is that not releasing kdevelop together with KDE 3.5 
branch means that we have to remove kdevelop translations from the kde-i18n 
tarballs. This issue should not be forgotten. 

Greetings,
Dirk

Re: Konqueror questions.

On Tuesday, 25. September 2007, Albert Astals Cid wrote:

> And if that's still not clear, that can well be because doing complex
> sentences in english is not my strong point, i'll rephrase it.
>
> I have "hope" we can have them "working" for KDE 4.0

I still don't get it. KDEPim 4. was not declared a show stopper for 4.0 
before. I agree that bugs in the libraries that are possibly exposed by 
kmail, but maybe also by other applications have to be fixed. but that is not 
the same level as saying "kmail is a ship stopper". 

There is nobody working on KDE Pim for 4.0, and with nobody working on it, the 
amount of time needed for getting it ready is definitely unpredictable. 

BTW: last time I tried to use kmail from KDE 4.0, it deleted all my folders. I 
was not too happy about that. (but I've learned meanwhile that for kmail, its 
always good to have backups). 

Greetings,
Dirk

Re: KDE 3.5.8

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

Re: KDE 3.5.8

At Monday 01 October 2007 02:17, you wrote:
> > 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

I don't want want to flame as you request, but could you consider moving kdevelop to extragear-sdk? In that
case you can determine for each release if you want to be part of it. We will just tag what is in there at that
moment so you can swap around whatever you see fit.

Again, just an idea, please don't kill me.

Toma
-- 
http://www.mailody.net

At Monday 01 October 2007 02:17, you wrote:
> > 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

I don't want want to flame as you request, but could you consider moving kdevelop to extragear-sdk? In that
case you can determine for each release if you want to be part of it. We will just tag what is in there at that
moment so you can swap around whatever you see fit.

Again, just an idea, please don't kill me.

Toma
--

-- 
http://www.mailody.net

Re: KDE 3.5.8

On Monday 01 October 2007, Tom Albers wrote:
> I don't want want to flame as you request, but could you consider
> moving kdevelop to extragear-sdk? In that case you can determine for
> each release if you want to be part of it. We will just tag what is
> in there at that moment so you can swap around whatever you see fit.

There is no need to move it anywhere, it just about deciding if KDevelop 
should or not be released together with a certain version of KDE. 
If the KDevelop developers tell in *advance* that we added new string, 
features, please don't include the current kdevelop module in KDE 
3.5.8, I don't think anybody will complain. The same the other way 
around, if they say that the only changes compared to the last released 
version are bugfixes, it can be included in the upcoming KDE pack.

Andras
--

-- 
Quanta Plus developer - http://quanta.kdewebdev.org
K Desktop Environment - http://www.kde.org

On Monday 01 October 2007, Tom Albers wrote:
> I don't want want to flame as you request, but could you consider
> moving kdevelop to extragear-sdk? In that case you can determine for
> each release if you want to be part of it. We will just tag what is
> in there at that moment so you can swap around whatever you see fit.

There is no need to move it anywhere, it just about deciding if KDevelop 
should or not be released together with a certain version of KDE. 
If the KDevelop developers tell in *advance* that we added new string, 
features, please don't include the current kdevelop module in KDE 

Re: KDE 3.5.8

Am Montag 01 Oktober 2007 schrieb Andras Mantia:
> On Monday 01 October 2007, Tom Albers wrote:
> > I don't want want to flame as you request, but could you consider
> > moving kdevelop to extragear-sdk? In that case you can determine for
> > each release if you want to be part of it. We will just tag what is
> > in there at that moment so you can swap around whatever you see fit.
>
> There is no need to move it anywhere, it just about deciding if KDevelop
> should or not be released together with a certain version of KDE.
> If the KDevelop developers tell in *advance* that we added new string,
> features, please don't include the current kdevelop module in KDE
> 3.5.8, I don't think anybody will complain. The same the other way
> around, if they say that the only changes compared to the last released
> version are bugfixes, it can be included in the upcoming KDE pack.

No. There _is_ a problem. And that is that KDE module's translations are
packaged in kde-i18n. So you can't simply translate kdevelop 7.0 in KDE 3.5's 
kde-i18n and then expect a working 3.5.8 to be released 

Greetings, Stephan

Re: KDE 3.5.8

At Monday 01 October 2007 10:09, you wrote:
> On Monday 01 October 2007, Tom Albers wrote:
> > I don't want want to flame as you request, but could you consider
> > moving kdevelop to extragear-sdk? In that case you can determine for
> > each release if you want to be part of it. We will just tag what is
> > in there at that moment so you can swap around whatever you see fit.
> 
> There is no need to move it anywhere, it just about deciding if KDevelop 
> should or not be released together with a certain version of KDE. 
> If the KDevelop developers tell in *advance* that we added new string, 
> features, please don't include the current kdevelop module in KDE 
> 3.5.8, I don't think anybody will complain. The same the other way 
> around, if they say that the only changes compared to the last released 
> version are bugfixes, it can be included in the upcoming KDE pack.

For the next release we will make releases of extragear application at the same time the other modules are
released. 
So your workflow fits way better in extragear (release on reqest at the same time as KDE) then a main module
(always release).

Toma
--

-- 
http://www.mailody.net

At Monday 01 October 2007 10:09, you wrote:
> On Monday 01 October 2007, Tom Albers wrote:
> > I don't want want to flame as you request, but could you consider
> > moving kdevelop to extragear-sdk? In that case you can determine for
> > each release if you want to be part of it. We will just tag what is
> > in there at that moment so you can swap around whatever you see fit.

Re: KDE 3.5.8

On Monday 01 October 2007, Stephan Kulow wrote:
> Am Montag 01 Oktober 2007 schrieb Andras Mantia:
> > On Monday 01 October 2007, Tom Albers wrote:
> > > I don't want want to flame as you request, but could you consider
> > > moving kdevelop to extragear-sdk? In that case you can determine
> > > for each release if you want to be part of it. We will just tag
> > > what is in there at that moment so you can swap around whatever
> > > you see fit.
> >
> > There is no need to move it anywhere, it just about deciding if
> > KDevelop should or not be released together with a certain version
> > of KDE. If the KDevelop developers tell in *advance* that we added
> > new string, features, please don't include the current kdevelop
> > module in KDE 3.5.8, I don't think anybody will complain. The same
> > the other way around, if they say that the only changes compared to
> > the last released version are bugfixes, it can be included in the
> > upcoming KDE pack.
>
> No. There _is_ a problem. And that is that KDE module's translations
> are packaged in kde-i18n. So you can't simply translate kdevelop 7.0
> in KDE 3.5's kde-i18n and then expect a working 3.5.8 to be released

So this would mean a need in scripty script each time a module (be it 
kdevelop, koffice or whatever) is packaged together or separately?
Can't the kde-i18n packages be created per module?
So let's say KDE 4.0 has kdelibs, kdepimlibs, kdebase and kdegames.
There will be kde-i18n-kdelibs, kde-i18n-kdepimlibs and so on.
If KDE 4.1 has one more module, the corresponding kde-i18n-* is also 
released. If a module is not released together with 4.2, the i18n 
module for that is not released.