On Friday, July 19, 2013 12:21:21 AM David Faure wrote:
> After more live discussion with Sebas and Marco plus Aaron over a video
> chat, we came up with the following setup for the workspace repos (*) :
>
> - the development branch for their next feature release (based on Qt5/KF5)
> will be "mast
El Divendres, 19 de juliol de 2013, a les 00:21:21, David Faure va escriure:
> After more live discussion with Sebas and Marco plus Aaron over a video
> chat, we came up with the following setup for the workspace repos (*) :
>
> - the development branch for their next feature release (based on Qt5
After more live discussion with Sebas and Marco plus Aaron over a video chat,
we came up with the following setup for the workspace repos (*) :
- the development branch for their next feature release (based on Qt5/KF5)
will be "master".
- *before* this happens, however, kdesrc-build / kde-build-
On Thursday 18 July 2013, Sebastian Kügler wrote:
> Hey,
>
> On Tuesday, July 16, 2013 22:03:51 Alexander Neundorf wrote:
> > On Tuesday 16 July 2013, Martin Graesslin wrote:
> > > On Monday 15 July 2013 14:42:14 Sebastian Kügler wrote:
> > > > On Tuesday, July 09, 2013 18:57:41 Albert Astals Cid
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/111576/
---
Review request for kdelibs and Àlex Fiestas.
Description
---
A simple
On Thursday, July 18, 2013 10:10:30 John Layt wrote:
> The general opinion on the mapping module is that the current design
> is overkill for most apps who just need to show where the user is
> located and don't need whizzy 3D views or routing information, etc.
QtPosition sounds great to me; mappi
On Thursday, July 18, 2013 10:42:35 Martin Graesslin wrote:
> On Thursday 18 July 2013 10:26:06 Sebastian Kügler wrote:
> > - master stays on 4.11, receives bugfixes, our releases are based on this
> >
> > branch and their version number will stay 4.11
>
> how do we prevent that people commit f
On Thursday, July 18, 2013 10:42:35 AM Martin Graesslin wrote:
> how do we prevent that people commit features into master?
Discipline? I assume the kde-workspace developers are all aware of the rules,
and they are busy working on frameworks branch. I doubt other KDE developers
would commit ther
Martin Graesslin wrote:
> how do we prevent that people commit features into master? I would prefer
To be honest, I haven't really seen people commit features into kdelibs, and
that's been frozen for a while.
--
Luca Beltrame - KDE Forums team
KDE Science supporter
GPG key ID: 6E1A4E79
Hey,
On Tuesday, July 16, 2013 22:03:51 Alexander Neundorf wrote:
> On Tuesday 16 July 2013, Martin Graesslin wrote:
> > On Monday 15 July 2013 14:42:14 Sebastian Kügler wrote:
> > > On Tuesday, July 09, 2013 18:57:41 Albert Astals Cid wrote:
> > > > So the kde-workspace dudes decided they don't w
On Thursday 18 July 2013 10:26:06 Sebastian Kügler wrote:
> - master stays on 4.11, receives bugfixes, our releases are based on this
> branch and their version number will stay 4.11
how do we prevent that people commit features into master? I would prefer if
we lock down master in gitolite so t
Hi all, especially workspace and frameworks hackers,
Based on our earlier discussion, I'd like to propose the following strategy as
a general way to move kde-workspace and related modules (such as kdeplasma-
adddons, etc.) to KF5 gradually:
- master stays on 4.11, receives bugfixes, our releases
[Apologies for cross-posting, please reply to kde-core-devel]
Hi,
At QtCS Torsten and I attended the QtLocation session to discuss the
future of the module. QtLocation was originally part of QtMobility
for Qt4 and was planned to be part of QtEssentials in Qt5, but it was
dropped from Qt5.0 due t
13 matches
Mail list logo
