headers
Allen Winter | 1 Jun 15:01
Picon
Favicon

Re: 3.5 Branch

On Tuesday 29 May 2007 6:10:52 am Stephan Kulow wrote:
> Am Samstag 26 Mai 2007 schrieb Clarence Dang:
> > On Saturday 26 May 2007 09:28, Cyrille Berger wrote:
> > > On Friday 25 May 2007, Clarence Dang wrote:
> > > > However, KDE 4 is not going to be released soon and even after it's
> > > > released,
> > >
> > > KDE4 isn't going to be released if people don't start to code for it.
> >
> > Sure.
> >
> > What I'm suggesting is keep the 3.5 branch open for commits and when enough
> > bugfixes have been done or X months have passed (where X is large), just do
> > another release.  However, don't open the 3.5 branch for adding more
> > features again :)
> 
> No more features, no more string changes, no more docu changes. That's my 
> idea. Bug fixes are allowed and after some time we'll do another maintenance 
> update 3.5.8 - e.g. in september.
> 

Since there have been no objections... I guess we have a decision.

Coolo, would you publicly announce this?
I know that the kdepim enterprise folks are very interested.

-Allen
Permalink | Reply | 0 comments |
headers
Allen Winter | 1 Jun 15:36
Picon
Favicon

kdepim 4.0 is a Yes!

Fellow Release Dudes,

June 1 is here.
And the consensus decision from the kdepim module is that
we will release with KDE 4.0.

The kdepim apps are set:
 - we are adding kmobiletools and kabcclient
 - we are removing kandy and kmobile
 - kpilot we removed, but has since been resurrected

-Allen, kdepim release dude
Permalink | Reply | 0 comments |
headers
Anne-Marie Mahfouf | 1 Jun 15:51
Picon
Favicon

Re: kdepim 4.0 is a Yes!

On Friday 1 June 2007 15:36:42 Allen Winter wrote:
> Fellow Release Dudes,
>
> June 1 is here.
> And the consensus decision from the kdepim module is that
> we will release with KDE 4.0.
>
> The kdepim apps are set:
>  - we are adding kmobiletools and kabcclient
>  - we are removing kandy and kmobile
>  - kpilot we removed, but has since been resurrected
>
> -Allen, kdepim release dude

Hi Pim release Dude,

Yeepee and congrats to your fellow hackers!

Anne-Marie
Permalink | Reply | 0 comments |
headers
Urs Wolfer | 1 Jun 16:49
Picon
Favicon

kdenetwork 4.0 release?

Hi all

I'm right now not sure what to do with the kdenetwork module... Not all apps 
are working very well atm. Matt Rogers (mattr) thinks that Kopete will not be 
ready for 4.0. KRDC is also not ready so far. Probably I will get it done for 
4.0. I don't know yet.

Apps that will be ready for sure are only Krfb and KGet. Filesharing and 
lanbrowsing: I have not tested them yet. Laurent Montel worked on them and 
thinks that they will be ready. Kppp seems to work, but I have no posibilty 
to test it.

I will drop the remaining apps (Kpf, KWifiManger, KDict) the next monday as I 
have written already a mail to this list.

What do you think? Should we release kdenetwork 4.0 and just disable the apps 
that are not ready in the release? (Of course, we are not going to release 
not working apps...) Or should we not release kdenetwork at all?

Bye
urs
Permalink | Reply | 4 comments |
headers
Eike Hein | 1 Jun 16:59

Re: kdenetwork 4.0 release?

Urs Wolfer wrote:
> What do you think? Should we release kdenetwork 4.0 and just disable the apps 
> that are not ready in the release? (Of course, we are not going to release 
> not working apps...) Or should we not release kdenetwork at all?

Well, it would be a shame not to release it for the
apps that you say do work or can be made to work in
time - krfb/krdc are used by quite a few people, and
having them disappear from 4.0 would be a fairly
significant regression. Also, the KGet guys seem to
have done an impressive amount of work for 4.0, and
if it's feasible, I'm sure they will want to get
that into the hands of people.

> Bye
> urs

--

-- 
Regards,
Eike Hein, hein@...
Permalink | Reply | 0 comments |
headers
Sebastian Kügler | 1 Jun 17:18
Picon
Favicon
Gravatar

Re: kdenetwork 4.0 release?

On Friday 01 June 2007 16:49:10 Urs Wolfer wrote:
> I'm right now not sure what to do with the kdenetwork module... Not all
> apps are working very well atm. Matt Rogers (mattr) thinks that Kopete will
> not be ready for 4.0. KRDC is also not ready so far. Probably I will get it
> done for 4.0. I don't know yet.
>
> Apps that will be ready for sure are only Krfb and KGet. Filesharing and
> lanbrowsing: I have not tested them yet. Laurent Montel worked on them and
> thinks that they will be ready. Kppp seems to work, but I have no posibilty
> to test it.
>
> I will drop the remaining apps (Kpf, KWifiManger, KDict) the next monday as
> I have written already a mail to this list.
>
> What do you think? Should we release kdenetwork 4.0 and just disable the
> apps that are not ready in the release? (Of course, we are not going to
> release not working apps...) Or should we not release kdenetwork at all?

What would be the added value of not releasing kdenetwork with 4.0 at all? Why 
is a module with three working apps in it (and which is likely to g row after 
4.0) insufficient to be added? To me, it sounds pretty normal that a) modules 
need to be slimmed down (because of lack of porting / maintainership) and b) 
at the beginning of a major release cycle, modules start off smaller.

IOW, why should "kopete is not ready for KDE4.0" affect kget getting in? 
AFAIK, technically there is no dependency.
--

-- 
sebas

 http://www.kde.org | http://vizZzion.org |  GPG Key ID: 9119 0EF9
(Continue reading)

Permalink | Reply | 2 comments |
headers
Allen Winter | 1 Jun 19:18
Picon
Favicon

Re: kdenetwork 4.0 release?

On Friday 01 June 2007 11:18:42 am Sebastian Kügler wrote:
> On Friday 01 June 2007 16:49:10 Urs Wolfer wrote:
> > I'm right now not sure what to do with the kdenetwork module... Not all
> > apps are working very well atm. Matt Rogers (mattr) thinks that Kopete will
> > not be ready for 4.0. KRDC is also not ready so far. Probably I will get it
> > done for 4.0. I don't know yet.
> >
> > Apps that will be ready for sure are only Krfb and KGet. Filesharing and
> > lanbrowsing: I have not tested them yet. Laurent Montel worked on them and
> > thinks that they will be ready. Kppp seems to work, but I have no posibilty
> > to test it.
> >
> > I will drop the remaining apps (Kpf, KWifiManger, KDict) the next monday as
> > I have written already a mail to this list.
> >
> > What do you think? Should we release kdenetwork 4.0 and just disable the
> > apps that are not ready in the release? (Of course, we are not going to
> > release not working apps...) Or should we not release kdenetwork at all?
> 
> What would be the added value of not releasing kdenetwork with 4.0 at all? Why 
> is a module with three working apps in it (and which is likely to g row after 
> 4.0) insufficient to be added? To me, it sounds pretty normal that a) modules 
> need to be slimmed down (because of lack of porting / maintainership) and b) 
> at the beginning of a major release cycle, modules start off smaller.
> 
> IOW, why should "kopete is not ready for KDE4.0" affect kget getting in? 
> AFAIK, technically there is no dependency.

I'm not a packager so I don't know, but...
does it makes distro packaging harder?  If there is no kdenetwork4.0
(Continue reading)

Permalink | Reply | 1 comment |
headers
Cyrille Berger | 1 Jun 20:06

Re: kdenetwork 4.0 release?

> I'm not a packager so I don't know, but...
> does it makes distro packaging harder?  If there is no kdenetwork4.0
> then the distro can ship a kdenetwork3.5.7 with apps that should
> work under the 4.0 desktop. i.e. they won't have to break out a
> separate kopete-3.5.7 + kdenetwork-4.0 ??
Kopete offers allready seperated tarball, so it might be not that a problem.

--

-- 
Cyrille Berger
Permalink | Reply | 0 comments |
headers
Tom Albers | 1 Jun 22:30
Picon

Re: KDE 3.5 Branch Freeze

Op vr 1 jun 2007 22:20 schreef u:
> Allen Winter napisa?(a):
> > Howdy,
> > 
> > The Release Team has decided that it is time to close the books on KDE 3.5.
> > 
> > To quote coolo:
> > "No more features, no more string changes, no more docu changes....
> > Bug fixes are allowed and after some time we'll do another maintenance 
> > update 3.5.8 - e.g. in september."
> > 
> > So bugfixes only from now on in the 3.5 branch.  If the bugfix requires
> > a string change, you will need to coordinate that change with the translators.
> > 
> > Onwards to KDE 4.0!
> 
> Great :/ You could have warned at least a week in advance...
> Can I commit the "switch application language" feature which has already
> been committed, but then reverted due to not being implemented in KDE 4?
> AFAIK it has already been ported to 4.0.

Seeing the history of this patch, I think it would be fair to make this one an exception and allow it.
Just my ho. What do others think?

Toma
Permalink | Reply | 3 comments |
headers
David Faure | 2 Jun 00:39
Picon
Favicon
Gravatar

Re: KDE 3.5 Branch Freeze

On Friday 01 June 2007, Tom Albers wrote:
> Op vr 1 jun 2007 22:20 schreef u:
> > Allen Winter napisa?(a):
> > > Howdy,
> > > 
> > > The Release Team has decided that it is time to close the books on KDE 3.5.
> > > 
> > > To quote coolo:
> > > "No more features, no more string changes, no more docu changes....
> > > Bug fixes are allowed and after some time we'll do another maintenance 
> > > update 3.5.8 - e.g. in september."
> > > 
> > > So bugfixes only from now on in the 3.5 branch.  If the bugfix requires
> > > a string change, you will need to coordinate that change with the translators.
> > > 
> > > Onwards to KDE 4.0!
> > 
> > Great :/ You could have warned at least a week in advance...
> > Can I commit the "switch application language" feature which has already
> > been committed, but then reverted due to not being implemented in KDE 4?
> > AFAIK it has already been ported to 4.0.
> 
> Seeing the history of this patch, I think it would be fair to make this one an exception and allow it.
> Just my ho. What do others think?

Ah, it saves a config key for the next app startup; good.
I had the wrong impression that it was trying to do runtime switching, which apps simply don't support.

I agree that this one could be allowed. It would be nice to see it ported to
kde4 at some point though...
(Continue reading)

Permalink | Reply | 2 comments |

Gmane