Hi,
I just finished uploading the first set of KDE 4.6.0 tarballs. It includes a
hotfix for the last showstopper bug, so we can continue. Thanks to Sebastian
and Will for debugging and working on the issue.
Release announcement might slip a bit given that we're quite late in the game,
thoug
On Thursday 20 January 2011, Rex Dieter wrote:
> On 01/20/2011 02:20 PM, Alexander Neundorf wrote:
> > On Thursday 20 January 2011, Rex Dieter wrote:
> >>> This is the code which would have to go into FindKDE4Internal.cmake in
> >>> case of breakage:
> >>
> >> Looks ok to me, just built kdebase-run
On Thursday 20 January 2011, Rex Dieter wrote:
> On 01/20/2011 02:20 PM, Alexander Neundorf wrote:
> > On Thursday 20 January 2011, Rex Dieter wrote:
> >>> This is the code which would have to go into FindKDE4Internal.cmake in
> >>> case of breakage:
> >>
> >> Looks ok to me, just built kdebase-run
On 01/20/2011 02:20 PM, Alexander Neundorf wrote:
> On Thursday 20 January 2011, Rex Dieter wrote:
>>> This is the code which would have to go into FindKDE4Internal.cmake in
>>> case of breakage:
>>
>> Looks ok to me, just built kdebase-runtime-4.5.95 with cmake-2.8.4-rc1
>> yesterday (is that a g
On Thursday 20 January 2011, Ian Monroe wrote:
> On Thu, Jan 20, 2011 at 14:05, Alexander Neundorf 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 an issu
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 Neundorf
wrote:
> >>> On Thursday 20 January 2011, Dirk Mueller wrote:
> On Wednesday 19 January
On Thu, Jan 20, 2011 at 14:05, Alexander Neundorf wrote:
> On Thursday 20 January 2011, Ian Monroe wrote:
>> On Thu, Jan 20, 2011 at 12:20, Alexander Neundorf wrote:
>> > On Thursday 20 January 2011, Dirk Mueller wrote:
>> >> On Wednesday 19 January 2011, Dirk Mueller wrote:
>> >> > so the genera
On Thursday 20 January 2011, Alexander Neundorf wrote:
> On Thursday 20 January 2011, Ian Monroe wrote:
> > On Thu, Jan 20, 2011 at 12:20, Alexander Neundorf
wrote:
> > > On Thursday 20 January 2011, Dirk Mueller wrote:
> > >> On Wednesday 19 January 2011, Dirk Mueller wrote:
> > >> > so the gene
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 Neundorf wrote:
>>> On Thursday 20 January 2011, Dirk Mueller wrote:
On Wednesday 19 January 2011, Dirk Mueller wrote:
> so the general consensus
On Thursday 20 January 2011, Ian Monroe wrote:
> On Thu, Jan 20, 2011 at 12:20, Alexander Neundorf 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 Thu, Jan 20, 2011 at 12:20, Alexander Neundorf 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 so
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
On Thu, Jan 20, 2011 at 08:18, Sebastian Trüg 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
___
release-team mailing
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 sch
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
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 app
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 comm
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
>
18 matches
Mail list logo
