Re: Python site packages

2013-01-20 Thread Kevin Kofler
On Sunday 20 January 2013 at 16:11:54, Michael Jansen wrote: > How about we make all of them happy? Your patch looks like the correct fix, can we please get this committed? Kevin Kofler ___ release-team mailing list release-team@kde.org https://

Re: Python site packages

2013-01-20 Thread Albert Astals Cid
El Diumenge, 20 de gener de 2013, a les 00:55:35, Kevin Kofler va escriure: > On Saturday 19 January 2013 at 22:33:19, David Faure wrote: > > Because this breaks "make install" for developers. > > > > (For the recommended case of installing as user rather than as root). > > The default should make

Re: Python site packages

2013-01-20 Thread Michael Jansen
On Sunday, January 20, 2013 08:37:28 PM Ben Cooksley wrote: > On Sun, Jan 20, 2013 at 12:55 PM, Kevin Kofler wrote: > > On Saturday 19 January 2013 at 22:33:19, David Faure wrote: > >> Because this breaks "make install" for developers. > >> > >> (For the recommended case of installing as user rat

Re: Re: Re: Re: KDE SC 4.11 Release Schedule

2013-01-20 Thread Martin Gräßlin
On Sunday 20 January 2013 11:55:00 David Edmundson wrote: > > So I did that - result is attached and it doesn't tell me anything except > > that in the 4.10 cycle significantly less bugs have been created than in > > the other cycles. > > Have you taken into account that the CONFIRMED status change

Re: Re: Re: KDE SC 4.11 Release Schedule

2013-01-20 Thread David Edmundson
On Sun, Jan 20, 2013 at 9:58 AM, Martin Gräßlin wrote: > On Saturday 19 January 2013 19:21:27 Martin Gräßlin wrote: >> > > I think that the 4.11 cycle was not optimal, but I think it is because >> > > it >> > > overlapps with Christmas and New Year. >> > >> > Why was that suboptimal? We've been ha

Re: Re: Re: KDE SC 4.11 Release Schedule

2013-01-20 Thread Martin Gräßlin
On Saturday 19 January 2013 19:21:27 Martin Gräßlin wrote: > > > I think that the 4.11 cycle was not optimal, but I think it is because > > > it > > > overlapps with Christmas and New Year. > > > > Why was that suboptimal? We've been having that since all the 4.x.odd > > releases > > I have the f