On Wednesday 19 January 2011, Dirk Mueller wrote:
so the general consensus seems to be against slipping the schedule and
inserting a RC3.
This means that we need to solve bug 246678. Given that there seems to be
no fix in sight (no comment in the last 14 days), can we mitigate it. is
there
On 01/20/2011 07:00 AM, Dirk Mueller wrote:
On Wednesday 19 January 2011, Dirk Mueller wrote:
so the general consensus seems to be against slipping the schedule and
inserting a RC3.
This means that we need to solve bug 246678. Given that there seems to be
no fix in sight (no comment in the
Tirsdag den 18. januar 2011 20:56:00 skrev Frank Reininghaus:
Am Dienstag 18 Januar 2011, 20:06:52 schrieb Aaron J. Seigo:
On Tuesday, January 18, 2011, Frank Reininghaus wrote:
Am Dienstag 18 Januar 2011, 17:57:01 schrieb Aaron J. Seigo:
There is a bug which lets some KDE apps
This patch does in no way solve the issue.
On 01/20/2011 02:00 PM, Dirk Mueller wrote:
On Wednesday 19 January 2011, Dirk Mueller wrote:
so the general consensus seems to be against slipping the schedule and
inserting a RC3.
This means that we need to solve bug 246678. Given that there
On Thursday 20 January 2011 14:53:19 Martin Schlander wrote:
Tirsdag den 18. januar 2011 20:56:00 skrev Frank Reininghaus:
Am Dienstag 18 Januar 2011, 20:06:52 schrieb Aaron J. Seigo:
On Tuesday, January 18, 2011, Frank Reininghaus wrote:
Am Dienstag 18 Januar 2011, 17:57:01 schrieb
On Thu, Jan 20, 2011 at 08:18, Sebastian Trüg tr...@kde.org wrote:
This patch does in no way solve the issue.
I'm not sure what the release team is supposed to do with this
statement. What do you think of 246678 and the 4.6.0 release?
Ian
___
On Thursday 20 January 2011, Dirk Mueller wrote:
On Wednesday 19 January 2011, Dirk Mueller wrote:
so the general consensus seems to be against slipping the schedule and
inserting a RC3.
This means that we need to solve bug 246678. Given that there seems to be
no fix in sight (no
On Thu, Jan 20, 2011 at 12:20, Alexander Neundorf neund...@kde.org wrote:
On Thursday 20 January 2011, Dirk Mueller wrote:
On Wednesday 19 January 2011, Dirk Mueller wrote:
so the general consensus seems to be against slipping the schedule and
inserting a RC3.
This means that we need to
On Thursday 20 January 2011, Ian Monroe wrote:
On Thu, Jan 20, 2011 at 12:20, Alexander Neundorf neund...@kde.org wrote:
On Thursday 20 January 2011, Dirk Mueller wrote:
On Wednesday 19 January 2011, Dirk Mueller wrote:
so the general consensus seems to be against slipping the schedule and
On 01/20/2011 02:05 PM, Alexander Neundorf wrote:
On Thursday 20 January 2011, Ian Monroe wrote:
On Thu, Jan 20, 2011 at 12:20, Alexander Neundorfneund...@kde.org wrote:
On Thursday 20 January 2011, Dirk Mueller wrote:
On Wednesday 19 January 2011, Dirk Mueller wrote:
so the general
On Thu, Jan 20, 2011 at 14:05, Alexander Neundorf neund...@kde.org wrote:
On Thursday 20 January 2011, Ian Monroe wrote:
On Thu, Jan 20, 2011 at 12:20, Alexander Neundorf neund...@kde.org wrote:
On Thursday 20 January 2011, Dirk Mueller wrote:
On Wednesday 19 January 2011, Dirk Mueller
On Thursday 20 January 2011, Rex Dieter wrote:
On 01/20/2011 02:05 PM, Alexander Neundorf wrote:
On Thursday 20 January 2011, Ian Monroe wrote:
On Thu, Jan 20, 2011 at 12:20, Alexander Neundorfneund...@kde.org
wrote:
On Thursday 20 January 2011, Dirk Mueller wrote:
On Wednesday 19
On Thursday 20 January 2011, Ian Monroe wrote:
On Thu, Jan 20, 2011 at 14:05, Alexander Neundorf neund...@kde.org wrote:
On Thursday 20 January 2011, Ian Monroe wrote:
...
Delaying 4.6.0 at this point due to a cmake that barely any distros
are using seems quite foolish to me (assuming it is
On Tuesday 18 January 2011, Dirk Mueller wrote:
Looks like we have two bugs marked as ship stopper: bug 246678 and 262274,
so just ignoring that is a bit of a problem for me :-)
Hi,
so the general consensus seems to be against slipping the schedule and
inserting a RC3.
This means that we
On Tuesday 18 January 2011 10:17:47 Dirk Mueller wrote:
how are the pros/cons regarding declaring the current 4.6 branch as 4.6.0
or adding another RC to the game?
Looks like we have two bugs marked as ship stopper: bug 246678 and 262274,
so just ignoring that is a bit of a problem for me
Hi,
Am Dienstag 18 Januar 2011, 10:17:47 schrieb Dirk Mueller:
how are the pros/cons regarding declaring the current 4.6 branch as 4.6.0
or adding another RC to the game?
There is a bug which lets some KDE apps (especially Dolphin) crash every time
they are closed:
On Tuesday, January 18, 2011, Frank Reininghaus wrote:
Hi,
Am Dienstag 18 Januar 2011, 10:17:47 schrieb Dirk Mueller:
how are the pros/cons regarding declaring the current 4.6 branch as 4.6.0
or adding another RC to the game?
There is a bug which lets some KDE apps (especially Dolphin)
On Tuesday 18 January 2011, Frank Reininghaus wrote:
Hi,
Am Dienstag 18 Januar 2011, 17:57:01 schrieb Aaron J. Seigo:
There is a bug which lets some KDE apps (especially Dolphin) crash every
time they are closed:
https://bugs.kde.org/show_bug.cgi?id=257944
has strigi devels
On Tuesday, January 18, 2011, Frank Reininghaus wrote:
Hi,
Am Dienstag 18 Januar 2011, 17:57:01 schrieb Aaron J. Seigo:
There is a bug which lets some KDE apps (especially Dolphin) crash
every time they are closed:
https://bugs.kde.org/show_bug.cgi?id=257944
has strigi devels
Am Dienstag 18 Januar 2011, 20:06:52 schrieb Aaron J. Seigo:
On Tuesday, January 18, 2011, Frank Reininghaus wrote:
Am Dienstag 18 Januar 2011, 17:57:01 schrieb Aaron J. Seigo:
There is a bug which lets some KDE apps (especially Dolphin) crash
every time they are closed:
On Tuesday 18 January 2011, Will Stephenson wrote:
Looks like we have two bugs marked as ship stopper: bug 246678 and
262274, so just ignoring that is a bit of a problem for me :-)
I've been testing a series of patches for trueg. We found one set that fix
246678 last week, but introduces
21 matches
Mail list logo
