--===============0502672430==
Content-Type: multipart/signed;
  boundary="nextPart1592530.DWHNB8HvYv";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

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

Hi,

ok, so KDE 4.0 has been delayed by around a month. Does this open another=20
window to do some string changes (if so, for how long), or does the string=
=20
freeze remain in effect?

On a more general note: I suppose for people who are highly involved in kde=
=20
development this will not be a problem, and the information is accessible=20
somewhere, but as an on-and-off contributor, I've found myself confused abo=
ut=20
what is or is not allowed at the moment, more than once. To me it would be=
=20
really helpful, if there was a large visible note right at the top of=20
http://techbase.kde.org/Schedules/KDE4/4.0_Release_Schedule (or some other=
=20
highly visible page), which always lists the freezes which are currently in=
=20
effect, and how long they are expected to stay in effect.

Regards
Thomas

--nextPart1592530.DWHNB8HvYv
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)

iD8DBQBHUtczEKRv+5DVNhgRAvT/AJ0ck+N9APacz353B+31wEsMOVoC/gCeOSCI
JRJYtgUhbh3DHsMHluTxidA=
=e44L
-----END PGP SIGNATURE-----

--nextPart1592530.DWHNB8HvYv--

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

--===============0502672430==--