On Wednesday 10 August 2011 11:49:29 Scott Kitterman wrote:
> My concern isn't minor API extensions that might be needed to fix
> a 4.7 bug, but with backporting new features to kdelibs 4.7 to support
> (rest of the SC) 4.8 development.
Right, we don't want that. The idea is there will not be n
On Wednesday, August 10, 2011 08:39:49 AM David Faure wrote:
> On Tuesday 09 August 2011 19:26:17 Scott Kitterman wrote:
> > On Tuesday, August 09, 2011 07:05:53 PM David Faure wrote:
> > > On Monday 08 August 2011 00:42:50 Scott Kitterman wrote:
> > > > On Saturday, August 06, 2011 09:32:02 AM Dav
On Tuesday 09 August 2011 19:26:17 Scott Kitterman wrote:
> On Tuesday, August 09, 2011 07:05:53 PM David Faure wrote:
> > On Monday 08 August 2011 00:42:50 Scott Kitterman wrote:
> > > On Saturday, August 06, 2011 09:32:02 AM David Faure wrote:
> > > ..
> > >
> > > > The next step is to backport
On Tuesday, August 09, 2011 07:05:53 PM David Faure wrote:
> On Monday 08 August 2011 00:42:50 Scott Kitterman wrote:
> > On Saturday, August 06, 2011 09:32:02 AM David Faure wrote:
> > ..
> >
> > > The next step is to backport the few bits of new api that went into
> > > master and that applicati
On Monday 08 August 2011 00:42:50 Scott Kitterman wrote:
> On Saturday, August 06, 2011 09:32:02 AM David Faure wrote:
> ..
>
> > The next step is to backport the few bits of new api that went into master
> > and that application developers started using, into the 4.7 branch of
> > kdelibs. I'll w
On Sunday 7 August 2011 08:58:46 Allen Winter wrote:
> On Sunday 07 August 2011 7:45:12 AM Stephen Kelly wrote:
> > I think maybe people didn't get the memo that there isn't going to be a
> > KDE 4.8?
> Huh? I am 100% against that plan.
>
> I can go along with saying that kdelibs is "done" at 4.7
On Saturday, August 06, 2011 09:32:02 AM David Faure wrote:
..
> The next step is to backport the few bits of new api that went into master
> and that application developers started using, into the 4.7 branch of
> kdelibs. I'll work on that, but help is welcome too.
...
This plan seems to be contr
Good point well made.
I think what you propose makes a lot of sense.
On 8/7/11, Michael Jansen wrote:
>> It might make sense to unfreeze master.
>>
>> $ git log --pretty=oneline master..
>> 4f0d3e Remove KGlobal::locale warning for pure Qt applications
>> 88836f add missing file
>> 63b8ad Implem
On Sunday 07 August 2011 13:45:12 Stephen Kelly wrote:
> It might make sense to unfreeze master.
>
> $ git log --pretty=oneline master..
> 4f0d3e Remove KGlobal::locale warning for pure Qt applications
> 88836f add missing file
> 63b8ad Implement locking on non-NFS systems using O_EXCL
> ea17ab ac
Albert Astals Cid wrote:
> On Diumenge 07 Agost 2011 12:45:12 Stephen Kelly wrote:
>> David Faure wrote:
>> > On Tuesday 07 June 2011 01:43:44 David Faure wrote:
>> >> Once the 4.7 branch is created, the plan is to do the following:
>> >>
>> >> - application developers can work in master as usual
On Sunday 07 August 2011 9:19:32 AM Aaron J. Seigo wrote:
> On Sunday, August 7, 2011 13:45:12 Stephen Kelly wrote:
> > I think maybe people didn't get the memo that there isn't going to be a
> > KDE4.8?
>
> there is going to be a KDE SC 4.8 release.
>
> but not another feature release of the Pl
On Sunday, August 7, 2011 13:45:12 Stephen Kelly wrote:
> I think maybe people didn't get the memo that there isn't going to be a
> KDE4.8?
there is going to be a KDE SC 4.8 release.
but not another feature release of the Platform (kdelibs, kde-runtime) called
4.8.
applications and workspaces
On Diumenge 07 Agost 2011 12:45:12 Stephen Kelly wrote:
> David Faure wrote:
> > On Tuesday 07 June 2011 01:43:44 David Faure wrote:
> >> Once the 4.7 branch is created, the plan is to do the following:
> >>
> >> - application developers can work in master as usual, no change there.
> >>
> >> - w
On Sunday 07 August 2011 7:45:12 AM Stephen Kelly wrote:
> I think maybe people didn't get the memo that there isn't going to be a KDE
> 4.8?
Huh? I am 100% against that plan.
I can go along with saying that kdelibs is "done" at 4.7 (bugfixes allowed)
and making future KDE 4 releases based on
> It might make sense to unfreeze master.
>
> $ git log --pretty=oneline master..
> 4f0d3e Remove KGlobal::locale warning for pure Qt applications
> 88836f add missing file
> 63b8ad Implement locking on non-NFS systems using O_EXCL
> ea17ab accept HTTP headers that are not followed by whitespace a
David Faure wrote:
> On Tuesday 07 June 2011 01:43:44 David Faure wrote:
>> Once the 4.7 branch is created, the plan is to do the following:
>>
>> - application developers can work in master as usual, no change there.
>>
>> - we create a new branch in kdelibs (say, "frameworks") for the work on
On Saturday 06 August 2011 10:10:16 Michael Pyne wrote:
> If you do use prefix just make sure the path is whereever you want kdelibs
> (frameworks branch) to be installed.
Sure; the reason I included the line is to encourage people to install
kdelibs-frameworks in a different prefix than the res
On Saturday, August 06, 2011 15:32:02 David Faure wrote:
> (*) Howto for kdesrc-build users:
>
> module kdelibs-frameworks
> repository kde:kdelibs
> branch frameworks
> cmake-options -DKDE4_BUILD_TESTS=TRUE -DCMAKE_BUILD_TYPE:STRING=debugfull
> -DCMAKE_PREFIX_PATH:PATH=/d/kde/inst/kdesuppor
On 08/06/2011 03:32 PM, David Faure wrote:
To say this clearly: NO COMMITS ARE POSSIBLE IN KDELIBS MASTER.
Sebas' proposal has finally been adopted, albeit with a minor
modification: Always winter in trunk! :-)
--
Best regards,
Eike Hein
On Tuesday 07 June 2011 01:43:44 David Faure wrote:
> Once the 4.7 branch is created, the plan is to do the following:
>
> - application developers can work in master as usual, no change there.
>
> - we create a new branch in kdelibs (say, "frameworks") for the work on
> splitting up kdelibs and
Hi everyone,
It's getting rather late here, so I'll skip introductions and get right to the
point :-)
Until 4.7 is branched, we keep fixing bugs in kdelibs 4, and work on trying to
get the things into Qt 5 that we need -- about 20 KDE-related people will be
going to the Qt Contributor Summit, t
21 matches
Mail list logo
