I wish I was there.
Scott K
Albert Astals Cid wrote:
>Just as a reminder, we have the Release Team BOF tomorrow July 17 at
>10:15 at
>Room A2
>
>Cheers,
> Albert
>
>El Dimarts, 16 de juliol de 2013, a les 14:38:47, Scott Kitterman va
>escriure:
>> On Monday, July 15, 2013 09:00:27 PM Luca Bel
Just as a reminder, we have the Release Team BOF tomorrow July 17 at 10:15 at
Room A2
Cheers,
Albert
El Dimarts, 16 de juliol de 2013, a les 14:38:47, Scott Kitterman va escriure:
> On Monday, July 15, 2013 09:00:27 PM Luca Beltrame wrote:
> > Àlex Fiestas wrote:
> > > Now that kde-workspace 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, July 15, 2013 09:00:27 PM Luca Beltrame wrote:
> Àlex Fiestas wrote:
> > Now that kde-workspace and kdelibs are going to be frozen (which in theory
> > means less work for everybody) I'd like to propose a new release schedule
> > to be applied starting with 4.12.
>
> Replying to the mes
On 07/15/2013 05:54 AM, Aaron J. Seigo wrote:
We are experimenting with the idea of a “long term release” version with kde-
workspace. If 4.11 gets widely used, deployed and stabalized (as we hope it
will) then blessing specific releases for extended #s of releases may be a good
approach.
Right
Àlex Fiestas wrote:
> Now that kde-workspace and kdelibs are going to be frozen (which in theory
> means less work for everybody) I'd like to propose a new release schedule
> to be applied starting with 4.12.
Replying to the message starting the thread because I forgot something
important at lea
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
Aaron J. Seigo wrote:
> translations .. this will require some time spent with the translation
> maintainers to figure out what will work well for those efforts.
The risk here is that when branches which have been in preparation for a long
time are merged, or simply many branches are merged, the a
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/111480/
---
(Updated July 16, 2013, 12:01 p.m.)
Status
--
This change has been ma
On Monday, July 15, 2013 11:51:38 Scott Kitterman wrote:
> 30 of the 42 weeks are spent in some kind of freeze state. Without process
> changes to get from "feature complete" to "released" there's no way to get
> to a three month cycle.
those of us in favour of a shorter development cycle are als
On Monday, July 15, 2013 14:16:01 Luca Beltrame wrote:
> Aaron J. Seigo wrote:
> > "we should try to recruit more people from the user community of
> > downstream distributions who have the skills necessary to merge patches
> > and test. some distributions do this already.”
>
> The reason I menti
> On July 15, 2013, 10:49 a.m., Aaron J. Seigo wrote:
> > i think that technically this is a bug in the applications triggering it,
> > but i agree we should probably work around it. the performance of the patch
> > is theoretically bad (linear time), but hopefully nobody is storing 1000s
> >
> On July 15, 2013, 10:49 a.m., Aaron J. Seigo wrote:
> > i think that technically this is a bug in the applications triggering it,
> > but i agree we should probably work around it. the performance of the patch
> > is theoretically bad (linear time), but hopefully nobody is storing 1000s
> >
16 matches
Mail list logo
