--===============0801082381==
Content-Type: multipart/signed;
  boundary="nextPart11975764.rjOh6mMhb3";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart11975764.rjOh6mMhb3
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Monday 21 April 2008 16:12:08 Dirk Mueller wrote:
> On Monday 21 April 2008, Aaron J. Seigo wrote:
> > * if we want WoC and other necessary steps forward in plasma in a
> > rational time frame (e.g. not next year), occassional blips like this
> > will happen and be necessary. bitching about how it will affect an
> > *alpha* release is shortsighted
>
> I have no pain in plasma being less than 100% functional for Alpha1, to be
> exact. The only question that is relevant (besides that I hurt your
> feelings again, I'm sorry really about that): does it help plasma
> development to get user feedback about the current (well todays+2 days)
> state of plasma or not? if you're saying "I don't want anyone to tell me
> about problems" right now, then we have to evaluate a different option. if
> you're saying "there are some problems but we'd still want to have some
> feedback) , then we're good to go.

Before the WoC merge, two people had worked on it, having it in (which real=
ly=20
was a group decision at the sprint) 'elevated its priority' and more people=
=20
joined in (locally at the sprint and on IRC). We got it back to something=20
that looks like a desktop pretty quickly. Although speculative, I doubt thi=
s=20
would have been possible when operating from a branch.

So yeah, pain, but worth it.

> It is an *alpha* release afterall, the amount of feedback it will receive
> will probably be fairly minimal anyway.

And we have a tradition of Alpha releases of Plasma, no? ;-)
=2D-=20
sebas

 http://www.kde.org | http://vizZzion.org |  GPG Key ID: 9119 0EF9=20

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iQEVAwUASAyuK2dNh9WRGQ75AQKN+gf+PuvtH5R1BIehcQ1bvsIhNInfZSpodBIK
1nPE/oyya6uPIPTH/LJBHFA1RoHfDpRwuUrJXD9QL7epSlT1St9Qjbn3d2OG5vFj
grZ3VejuXxK53UYzdJRRiFTv94vlCXc3tQICgsJ6LTVe63lcLg9KweF7CU09i/Zx
8kbOHu376j1crklqLiL0z6tQ+Yi6EYnb6XMsuzVmPAFdYLmv0J7U9zAsZMv3V5pq
igAneW9m/MKWfHgD2sbY07+5Jzv7u5VTzFhYIUOWy5uVb6ziEGHf6Zl/+eiqqzgE
qcqCv7B8ICmuOiP/HlY65+inGsPtp9kt2wMdvm0yq+L+7eHYX5Ia/A==
=vbGZ
-----END PGP SIGNATURE-----

--nextPart11975764.rjOh6mMhb3--

--===============0801082381==
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

--===============0801082381==--