--nextPart18659821.Lugh0EPbIm
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Monday 05 January 2009, Aaron J. Seigo wrote:
> On Monday 05 January 2009, Sebastian K=FCgler wrote:
> > On Monday 05 January 2009 18:53:31 Aaron J. Seigo wrote:
> > >   On Monday 05 January 2009, Sebastian K=FCgler wrote:
> > > > On Monday 05 January 2009 16:47:22 Albert Astals Cid wrote:
> > > > > > That said, I've been thinking if the release schedule
> > > > > > policy for kdeplasma- addons shouldn't be relaxed. I don't
> > > > > > see any real problems for reviewed and tested code to move
> > > > > > there, even after the rest of KDE is frozen -- but until
> > > > > > further notice, it's subject to freeze.
> > > > >
> > > > > I really don't see why kdeplasma-addons should be different
> > > > > from the rest of KDE.
> > > >
> > > > Maybe not kdeplasma-addons, but it'd surely be nice to have a
> > > > way to release applets in between cycles, a bit like extragear.
> > > > What I don't like
> > >
> > > we used to have an extragear repo for plasma stuff, but it became
> > > kdeplasma- addons instead because it was "too hard" for people to
> > > keep up between versions as BC was breaking in libplasma. just
> > > sounds like we need to start up the extragear again for plasma,
> > > though that makes kdeplasma-addons a bit of an odd duckling then.
> > >
> > > personally i don't think there's a lot of reason for another
> > > module, though.
> >
> > Or maybe intermittent releases of kdeplasma-addons? Like once every
> > two months, with two weeks of freeze? Would make for nice testing
> > ground of seasoned releases as well ...
>
> yes, that would be nice indeed given the rate of change those tend to
> have =3D)

Will the rate of changes still be so high if libplasma is frozen for six=20
months? Who wants to write applets for a frozen library when the=20
version in trunk has so many cool new features one could play with? ;-)

Also, what happened to the idea to install the applets via ghns instead=20
of relying on the applets to be packaged by all distros. I thought the=20
applets where supposed to be platform-independent, i.e. script code=20
with some SVG graphics.

=46urthermore, what's the point of making a release every two months given=
=20
that the big distros all have a six months schedule, so that the=20
majority of our users have no advantage of a two months release cycle?=20
(Yes, they might have a small advantage if their distro's release cycle=20
is shifted some months w.r.t. our release cycle.) Only a very small=20
fraction of our users use repositories that provide intermediate=20
updates.

So unless _we_ provide ready-to-install versions of those applets for=20
the major distros (which is said to be trivial with openSUSE's build=20
service) a two months schedule doesn't make much sense to me.

This is all IMO.

Oh. One more thing. If you already do intermittent releases yourself why=20
not do all releases yourself (which brings us back to extragear)?


Hugs, love and peace,
Ingo

--nextPart18659821.Lugh0EPbIm
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEABECAAYFAkliYPcACgkQGnR+RTDgudgrZQCbBk+EBk7Z4qt74dwADpyoEe5j
UxgAoIAVclyimd9TD8pRhR8k58lpswDV
=E1ld
-----END PGP SIGNATURE-----

--nextPart18659821.Lugh0EPbIm--