--===============0708270032==
Content-Type: multipart/signed;
  boundary="nextPart3653313.H5hxn6S3c7";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart3653313.H5hxn6S3c7
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Sunday 20 April 2008, Matt Rogers wrote:
> On Sunday 20 April 2008 06:09:22 Tom Albers wrote:
> > Hi Guys,
> >
> > On the agenda for this week is the tagging of Alpha 1. As I understand
> > from IRC the fallout from the plasma hacking event is pretty big and the
> > current state is less than what we want to display to our alpha testing
> > user base.

indeed. i hope to have most of the fallout under control by end of week, bu=
t=20
one never knows. it could take longer, it could also go really quickly. the=
=20
taskbar and system tray were working great, but currently .. aren't.

> > I know KDE is /a lot/ more than plasma, but I feel the overall percepti=
on
> > of KDE in reviews and perception of users is largely based on Plasma. I

one hopes an alpha won't get reviews, per say. but it is true that plasma=20
needs to be at least basically usable for the alpha to be testable by most=
=20
people (as most people won't mix/match their kde4 testing installs).

> Delaying Alpha 1 is not the way to go, IMHO. We need to push Alpha 1 out
> and send the signals to everybody that it's time to get in to release mod=
e.

well, except that shipping plasma in the current state is a bit silly, even=
 if=20
it is an alpha. most of the applets outside of kdebase are not buildable,=20
several of the applets in kdebase are broken (apparently we have issues wit=
h=20
QGraphicsProxyWidget and system tray). there's really no way people will us=
e=20
it at all in its current state.

i do agree that the alpha shouldn't be delayed, however, for everyone else'=
s=20
sake.

personally, i'd recommend shipping alpha1 with plasma from, say, april 10th.

that way the alpha isn't delayed for the rest of the code base and the plas=
ma=20
devs can get the code base under control. i'm back to hacking tomorrow and=
=20
will be diving immediately into systray and taskbar. those could end up bei=
ng=20
one-day fixes, in which case the alpha tagging could go ahead on the 22nd.

but a contingency for a plasma (or even workspace as a whole if that's easi=
er?=20
crappy for the kwin guys though =3D/ ) from the 10th is probably smart.

and apologies for needing the weekend off around release time; after the=20
sprint, board meetings and then adjusting 8 time zones (plus the laundry,=20
groceries, etc that come with being back) i just needed a couple days.

=2D-=20
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Trolltech

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

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

iD8DBQBIC4tL1rcusafx20MRAvy3AJ0aHiV8hQVEt/9i5y36DPZnRpqFKgCfTVGW
RJNbLUrb+vGIuCSVp0NU6kE=
=AAit
-----END PGP SIGNATURE-----

--nextPart3653313.H5hxn6S3c7--

--===============0708270032==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

--===============0708270032==--