On Tuesday 19 June 2012 14.51.03 Anne-Marie Mahfouf wrote:
> On 06/18/2012 07:47 PM, Torgny Nyblom wrote:
> > On Monday 18 June 2012 19.08.33 Albert Astals Cid wrote:
> >> El Dilluns, 18 de juny de 2012, a les 06:36:33, Martin Gräßlin va escriure:
> >>> On Monday 18 June 2012 00:26:13 Albert Astals
On 06/18/2012 07:47 PM, Torgny Nyblom wrote:
On Monday 18 June 2012 19.08.33 Albert Astals Cid wrote:
El Dilluns, 18 de juny de 2012, a les 06:36:33, Martin Gräßlin va escriure:
On Monday 18 June 2012 00:26:13 Albert Astals Cid wrote:
My concerns:
* Need more people to do the tarball packagi
On Friday, June 15, 2012 01:05:44 PM Sebastian Kügler wrote:
> Hi all,
>
> During our sprint in Pineda de Mar, we sat down and thought about how our
> release cycles relate to the structures in our software, we came up with the
> following proposal we'd like you to consider and provide feedback ab
> * The difficulty of coding for N releases. Since the releases an not aligned
> anymore, you have to maintain code and #ifdefs for new features that depend on
> new versions of parts X of the stack that may or might not be used by people
> compiling the application. We've have some bad experience
On Monday, June 18, 2012 19:21:29 Andreas K. Huettel wrote:
> > > know the current state of the release and commit new features or new
> > > strings when we are frozen, and that's with just one release schedule, i
> > > can imagine the mess with N different release schedules
> >
> > "Always summer
On Monday 18 June 2012 19.08.33 Albert Astals Cid wrote:
> El Dilluns, 18 de juny de 2012, a les 06:36:33, Martin Gräßlin va escriure:
> > On Monday 18 June 2012 00:26:13 Albert Astals Cid wrote:
> > > My concerns:
> > > * Need more people to do the tarball packaging/releasing (since if you
> > >
> > know the current state of the release and commit new features or new
> > strings when we are frozen, and that's with just one release schedule, i
> > can imagine the mess with N different release schedules
>
> "Always summer in trunk". As long as releases are not created from the
> master bran
On Monday 18 June 2012 19:08:33 Albert Astals Cid wrote:
> El Dilluns, 18 de juny de 2012, a les 06:36:33, Martin Gräßlin va escriure:
> > On Monday 18 June 2012 00:26:13 Albert Astals Cid wrote:
> > > My concerns:
> > > * Need more people to do the tarball packaging/releasing (since if you
> > >
El Dilluns, 18 de juny de 2012, a les 06:36:33, Martin Gräßlin va escriure:
> On Monday 18 June 2012 00:26:13 Albert Astals Cid wrote:
> > My concerns:
> > * Need more people to do the tarball packaging/releasing (since if you
> >
> > propose to release that often you can't expect the same person
On Monday, June 18, 2012 00:26:13 Albert Astals Cid wrote:
> * Need more people to do the tarball packaging/releasing (since if you
> propose to release that often you can't expect the same person to be doing
> packages almost weekly or byweekly given the release dates won't probably
> align)
>
On Monday 18 June 2012 00:26:13 Albert Astals Cid wrote:
> My concerns:
>
> * Need more people to do the tarball packaging/releasing (since if you
> propose to release that often you can't expect the same person to be doing
> packages almost weekly or byweekly given the release dates won't probab
El Divendres, 15 de juny de 2012, a les 13:05:44, Sebastian Kügler va
escriure:
> Hi all,
Hi
> During our sprint in Pineda de Mar, we sat down and thought about how our
> release cycles relate to the structures in our software, we came up with the
> following proposal we'd like you to consider a
Ahoy,
On Fri, Jun 15, 2012 at 1:05 PM, Sebastian Kügler wrote:
> Starting with KDE Frameworks 5, we will release Frameworks, Workspaces and
> Applications each with their own release cycles. Each of these releases would
> be a set of tarballs of the latest stable versions of the application (or
>
Am 16.06.2012, 06:25 Uhr, schrieb Scott Kitterman :
On Friday, June 15, 2012 01:05:44 PM Sebastian Kügler wrote:
As an example, Frameworks could release updates every 2 months, while
our
application collection is updated monthly. New iterations of the
workspaces
come every four months. (Th
i like where this is going..i've always wanted a bit more flexibility
in releases...
one thing to keep in mind (i realize it's a bit premature to say this,
but..) we'd definitely have to make sure we coordinate the various
freezes well, since there'd be a dedicated and specialized
freeze-timeline
On Friday, June 15, 2012 01:05:44 PM Sebastian Kügler wrote:
> Hi all,
>
> During our sprint in Pineda de Mar, we sat down and thought about how our
> release cycles relate to the structures in our software, we came up with the
> following proposal we'd like you to consider and provide feedback ab
Hi all,
During our sprint in Pineda de Mar, we sat down and thought about how our
release cycles relate to the structures in our software, we came up with the
following proposal we'd like you to consider and provide feedback about.
Starting with KDE Frameworks 5, we will release Frameworks, Wor
17 matches
Mail list logo
