--nextPart11534500.LQhIyx1EUS
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hallo folks,

as you most certainly have read multiple times already, KDE PIM will not be=
=20
part of the KDE SC 4.5.0 release due to not having reached the necessary=20
stability yet.

Basically our focus for as long as it takes is to work almost [1] exclusive=
ly=20
on the 4.5 branch and forward porting fixes to trunk.

Now, some of the issues we are facing are hard or maybe even impossible to =
fix=20
without changing the UI, which would potentially mean changes in strings.

Of course we won't do something like this before the KD SC 4.5.0 release as=
=20
you have already your hands full for that.

However, I'd like to ask whether in principle you would agree on letting us=
=20
change/introduce strings in KDEPIM after that.
And if yes, what kind of freeze period would be required before the PIM=20
release?

Cheers,
Kevin

[1] Some things like folding back things from e.g. the Google Summer of Cod=
e=20
branch or the mobile branch are happening in trunk in parallel.
=2D-=20
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring

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

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

iD8DBQBMSH7+nKMhG6pzZJIRAoATAJ4hu1ahez1R6GVnlcOYwqfxEKOdFACdHPF9
H0nuQZGjaAYSVtPo7G0W+Ho=
=YQjk
-----END PGP SIGNATURE-----

--nextPart11534500.LQhIyx1EUS--