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
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 Monday 15 July 2013 14:42:14 Sebastian Kügler wrote:
> - It will likely be impossible to merge frameworks into master later
This is complete FUD.
If you regularly merge bugfixes from master to frameworks (surely you want to
do that, right?),
then merging frameworks to master is completely tri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
David Faure wrote:
>> > *Minimize disruption*
>> For whom?
>
> For all the developers and users who compile KDE from sources, for
> packagers, etc.
I can say +1 to that. Stuff like Project Neon or some things we're trying to
do in openSUSE to *ea
On Wed, July 17, 2013 22:24:52 Ben Cooksley wrote:
> Hi all,
>
> Just a side note here: using any branch name other than 'frameworks'
> for KF5 based development in kde-workspace will throw a wrench in the
> tools which depend on the KDE dependency metadata file. This includes
> the CI system and
Hi all,
Just a side note here: using any branch name other than 'frameworks'
for KF5 based development in kde-workspace will throw a wrench in the
tools which depend on the KDE dependency metadata file. This includes
the CI system and kdesrc-build as well to a certain extent.
Fixing this will req
On Monday 15 July 2013 12:27:53 Aaron J. Seigo wrote:
> So please excuse me if I don’t base my thoughts on your input on how to
> maintain a module.
WTF? This is a very very low blow.
I recognize that the *initial* solution for kdelibs was broken and a bad idea.
This is why we're not doing that a
On Tuesday 16 July 2013, Martin Graesslin wrote:
> On Monday 15 July 2013 14:42:14 Sebastian Kügler wrote:
> > Hey,
> >
> > On Tuesday, July 09, 2013 18:57:41 Albert Astals Cid wrote:
> > > So the kde-workspace dudes decided they don't want a 4.12 release and
> > > that they'll do a LTS 4.11, fine
On Monday 15 July 2013 14:42:14 Sebastian Kügler wrote:
> Hey,
>
> On Tuesday, July 09, 2013 18:57:41 Albert Astals Cid wrote:
> > So the kde-workspace dudes decided they don't want a 4.12 release and that
> > they'll do a LTS 4.11, fine, how do we fix that branch wise?
>
> After carefully readin
On Monday, July 15, 2013 10:15:10 Michael Pyne wrote:
> On Mon, July 15, 2013 12:27:53 Aaron J. Seigo wrote:
> > On Saturday, July 13, 2013 23:36:24 David Faure wrote:
> > Doing a 4.12 / 4.13 makes that infeasible: it would mean continuing to
> > track the 4.11 branch *and* master *and* the Qt5 br
On Monday, July 15, 2013 10:18:17 Michael Pyne wrote:
> That (or something like it) would be wonderful.
ok; so we have a potential winner unless someone produces a valid objection.
since a move to Qt5/Frameworks5 for master inherently brings this breakage
with it, we’ll simply need to produce an
On Monday, July 15, 2013 20:00:39 Thomas Lübking wrote:
> But KDE has ever released as block and so far still releases as block.
this is a non-argument. otherwise we will forever keep the SC together exactly
as it is. flexibility can be useful.
> If now ppl. get "mostly block and some bits of ol
On Monday 15 Jul 2013 09:46:49 Aaron J. Seigo wrote:
> On Friday, July 12, 2013 17:48:50 David Jarvie wrote:
> > best of intentions) for old habits to take over and to accidentally use
> > master again. This happened to me more than once.
>
> So how can we make that clearer for people and hard fo
On Freitag, 12. Juli 2013 17:47:53 CEST, Aaron J. Seigo wrote:
On Wednesday, July 10, 2013 22:39:29 Thomas Lübking wrote:
There'll have to be (minor) patches to kde-workspace (you cannot keep
shipping known and fixable crashes), thus new tarballs and
shipping kdelibs
4.13.2, workspace 4.11.12
On Mon, July 15, 2013 10:46:49 Aaron J. Seigo wrote:
> On Friday, July 12, 2013 17:48:50 David Jarvie wrote:
> > best of intentions) for old habits to take over and to accidentally use
> > master again. This happened to me more than once.
>
> So how can we make that clearer for people and hard fo
On Mon, July 15, 2013 12:27:53 Aaron J. Seigo wrote:
> On Saturday, July 13, 2013 23:36:24 David Faure wrote:
> > * let master be the branch that will become 4.12, even if you (= the
> > workspace developers) don't intend to do more than bugfixing on 4.x, there
> > will always be a need to separate
Hey,
On Tuesday, July 09, 2013 18:57:41 Albert Astals Cid wrote:
> So the kde-workspace dudes decided they don't want a 4.12 release and that
> they'll do a LTS 4.11, fine, how do we fix that branch wise?
After carefully reading everybody's opinion, I would like to make kde-
workspace master our
On Saturday, July 13, 2013 23:36:24 David Faure wrote:
> I feel strongly about what kde-workspace should do in the current situation,
> actually, after having gone through multiple solutions with kdelibs:
Welcome to my world.
I feel strongly about what kdelibs should have done. I am not the maint
On Friday, July 12, 2013 17:48:50 David Jarvie wrote:
> On Fri, July 12, 2013 4:42 pm, Aaron J. Seigo wrote:
> > * there were 2 main reasons the branched-kdelibs shifted back to master-
> >
> > kdelibis:
> > * people were too stubborn and too (willfully) uninformed to understand
> >
> > why t
On Sat, July 13, 2013 23:36:24 David Faure wrote:
> No changes to anyone's workflow, including translators, testers, powerusers,
> distros, kde-wide bugfixers, etc. The only ones who have to switch to
> another branch is the people switching to a qt5/frameworks based
> development, and these people
On Thursday 11 July 2013 11:55:54 Sebastian Kügler wrote:
> I'd be in favor of moving master to Qt5/Frameworks5 soonish:
>
> - I don't want to have to keep track of merging between 3 branches, 2 is
> really enough
> - kde-workspace developers have decided to move onto Frameworks5 after 4.11
> i
On Fri, July 12, 2013 4:42 pm, Aaron J. Seigo wrote:
> * there were 2 main reasons the branched-kdelibs shifted back to master-
> kdelibis:
> * people were too stubborn and too (willfully) uninformed to understand
> why this was a useful thing and just kept pelting it with stop energy at
> ev
On Friday, July 12, 2013 05:52:02 PM Aaron J. Seigo wrote:
> On Wednesday, July 10, 2013 15:34:43 Michael Jansen wrote:
> > Because of that it should be announced. BIG TIME. I am not hopeful because
>
> agreed. so what i’d like to see is a definitive listing of all the places
> that this should be
On Tuesday, July 9, 2013 23:45:39 Martin Graesslin wrote:
> If someone wants to do a 4.12 release from kde-workspace module it can be
> branched from the 4.11 branch.
fwiw, i take no responsibility for branches other than the 4.11 one. if
someone feels the burning urge to make a release 4.12, i’d
On Wednesday, July 10, 2013 15:34:43 Michael Jansen wrote:
> Because of that it should be announced. BIG TIME. I am not hopeful because
agreed. so what i’d like to see is a definitive listing of all the places that
this should be announced and in what form. since i’ve gotten this wrong enough
ti
On Wednesday, July 10, 2013 22:39:29 Thomas Lübking wrote:
> There'll have to be (minor) patches to kde-workspace (you cannot keep
> shipping known and fixable crashes), thus new tarballs and shipping kdelibs
> 4.13.2, workspace 4.11.12 ("depending" on kdelibs 4.13.2) and kde-runtime
> 4.13.2 does
On Thursday, July 11, 2013 12:37:39 Frank Reininghaus wrote
> Merging frameworks into master in kdelibs has the following
> disadvantages from my point of view (besides the "makes it harder for
i agree; the window for doing this closed a while ago. we’ve made some poor
decisions that we need to l
On Friday, July 12, 2013 10:19:45 Andras Mantia wrote:
> On Thursday, July 11, 2013 07:41:37 AM Martin Gräßlin wrote:
> > I agree that this is
> >
> > something we learned from kdelibs that we need to keep the releases going
> > even if they do not contain new features.
>
> With kdelibs didn't
On Thursday, July 11, 2013 07:41:37 AM Martin Gräßlin wrote:
> I agree that this is
> something we learned from kdelibs that we need to keep the releases going
> even if they do not contain new features.
With kdelibs didn't we switch back to branch and tag it from master even
though master is
Hi,
2013/7/11 Sebastian Kügler:
> Hi,
>
> On Tuesday, July 09, 2013 23:45:39 Martin Graesslin wrote:
>> On Tuesday 09 July 2013 18:57:41 Albert Astals Cid wrote:
>> > So the kde-workspace dudes decided they don't want a 4.12 release and that
>> > they'll do a LTS 4.11, fine, how do we fix that bra
Hi,
On Tuesday, July 09, 2013 23:45:39 Martin Graesslin wrote:
> On Tuesday 09 July 2013 18:57:41 Albert Astals Cid wrote:
> > So the kde-workspace dudes decided they don't want a 4.12 release and that
> > they'll do a LTS 4.11, fine, how do we fix that branch wise?
>
> I don't see how that affec
On Wednesday, July 10, 2013 01:25:06 Andras Mantia wrote:
> On Tuesday, July 09, 2013 11:45:39 PM Martin Graesslin wrote:
> > * master is opened for feature development and will lead to Plasma
> > Workspaces 2 (or whatever the release will be called in the end).
>
> Does this mean that kde-worksp
On Wednesday 10 July 2013 22:39:29 Thomas Lübking wrote:
> On Mittwoch, 10. Juli 2013 21:58:34 CEST, Albert Astals Cid wrote:
> >> Those who want to develop on or use it will hopefully find it
> >> and others can
> >> continue to use master as it is. (And where important bugfixes etc. for
> >> 4.12
On Mittwoch, 10. Juli 2013 22:39:01 CEST, Scott Kitterman wrote:
I thought you said in the 3 month release cycle discussion that
every module
I think this discussion in unrelated to the new release cycle thread.
Frozen workspace and the question what to do with the branches in kde-workspace
On Wednesday, July 10, 2013 09:58:34 PM Albert Astals Cid wrote:
> El Dimecres, 10 de juliol de 2013, a les 15:55:01, Thomas Lübking va
escriure:
> > On Mittwoch, 10. Juli 2013 15:34:43 CEST, Michael Jansen wrote:
> > > Because of that it should be announced. BIG TIME.
> >
> > I'd suggest to keep
On Mittwoch, 10. Juli 2013 21:58:34 CEST, Albert Astals Cid wrote:
Those who want to develop on or use it will hopefully find it
and others can
continue to use master as it is. (And where important bugfixes etc. for
4.12 can go)
But there's not going to be a kde-workspace 4.12 as announced a
El Dimecres, 10 de juliol de 2013, a les 15:55:01, Thomas Lübking va escriure:
> On Mittwoch, 10. Juli 2013 15:34:43 CEST, Michael Jansen wrote:
> > Because of that it should be announced. BIG TIME.
>
> I'd suggest to keep master as it is and develop PWv2 in a new branch.
>
> Those who want to de
On Mittwoch, 10. Juli 2013 15:34:43 CEST, Michael Jansen wrote:
Because of that it should be announced. BIG TIME.
I'd suggest to keep master as it is and develop PWv2 in a new branch.
Those who want to develop on or use it will hopefully find it and others can
continue to use master as it is
On Wednesday, July 10, 2013 02:12:41 PM David Jarvie wrote:
> On Wed, July 10, 2013 1:19 pm, Martin Graesslin wrote:
> > On Wednesday 10 July 2013 01:25:06 Andras Mantia wrote:
> >> On Tuesday, July 09, 2013 11:45:39 PM Martin Graesslin wrote:
> >> > * master is opened for feature development and w
On Wed, July 10, 2013 1:19 pm, Martin Graesslin wrote:
> On Wednesday 10 July 2013 01:25:06 Andras Mantia wrote:
>> On Tuesday, July 09, 2013 11:45:39 PM Martin Graesslin wrote:
>> > * master is opened for feature development and will lead to Plasma
>> > Workspaces 2 (or whatever the release will
On Wednesday 10 July 2013 01:25:06 Andras Mantia wrote:
> On Tuesday, July 09, 2013 11:45:39 PM Martin Graesslin wrote:
> > * master is opened for feature development and will lead to Plasma
> > Workspaces 2 (or whatever the release will be called in the end).
>
> Does this mean that kde-workspac
On Tuesday, July 09, 2013 11:45:39 PM Martin Graesslin wrote:
> * master is opened for feature development and will lead to Plasma
> Workspaces 2 (or whatever the release will be called in the end).
Does this mean that kde-workspace in master will exists, but with a different
content (and I assu
On Tuesday 09 July 2013 18:57:41 Albert Astals Cid wrote:
> So the kde-workspace dudes decided they don't want a 4.12 release and that
> they'll do a LTS 4.11, fine, how do we fix that branch wise?
I don't see how that affects branching.
* 4.11 is branched from master
* master is opened for feature
43 matches
Mail list logo
