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
El Dimecres, 17 de juliol de 2013, a les 19:34:17, Scott Kitterman va
escriure:
> On Thursday, July 18, 2013 01:19:12 AM Albert Astals Cid wrote:
> > El Dimecres, 17 de juliol de 2013, a les 07:37:16, Luca Beltrame va
>
> escriure:
> > > Albert Astals Cid wrote:
> > > > Just as a reminder, we hav
On Thursday, July 18, 2013 01:19:12 AM Albert Astals Cid wrote:
> El Dimecres, 17 de juliol de 2013, a les 07:37:16, Luca Beltrame va
escriure:
> > Albert Astals Cid wrote:
> > > Just as a reminder, we have the Release Team BOF tomorrow July 17 at
> > > 10:15
> > > at Room A2
> >
> > Would it be
El Dimecres, 17 de juliol de 2013, a les 12:03:53, Jaime Torres Amate va
escriure:
> Why not the other direction?
> 4 months to develop new features, 2 months freeze and fixing?
Because this doesn't move in the direction most of the people agreed we want
(shorter releases, more candence).
Cheer
El Dimecres, 17 de juliol de 2013, a les 07:37:16, Luca Beltrame va escriure:
> Albert Astals Cid wrote:
> > Just as a reminder, we have the Release Team BOF tomorrow July 17 at 10:15
> > at Room A2
>
> Would it be possible to post the outcome of the discussion here? It would be
> very helpful (as
-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
Albert Astals Cid wrote:
> Just as a reminder, we have the Release Team BOF tomorrow July 17 at 10:15
> at Room A2
Would it be possible to post the outcome of the discussion here? It would be
very helpful (as unfortunately I'm not in Bilbao).
--
Luca Beltrame - KDE Forums team
KDE Science supp
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
Why not the other direction?
4 months to develop new features, 2 months freeze and fixing?
Jonathan Riddell escribió:
>
>Albert Astals Cid:
>idea is to shorten release
>we have now lots of freezes and a branch
>alex wants something shorter, suggested 3 months between release with
>only 1
Albert Astals Cid:
idea is to shorten release
we have now lots of freezes and a branch
alex wants something shorter, suggested 3 months between release with only
1 month of freezes
put all freezes together on same date, release beta 1, in two weeks RC 1,
in 2 weeks more release
On Wednesday, July 17, 2013 11:21:23 AM Volker Krause wrote:
> seven years ago I accidentally ended up as the maintainer of the Akonadi
> server. Caring a lot about Akonadi but lacking the time to properly do my
> maintainer duties anymore I'm very happy we now have a very dedicated and
> skilled
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
13 matches
Mail list logo
