From kde-pim  Fri Nov 28 06:09:14 2014
From: "Aaron J. Seigo" <aseigo () kde ! org>
Date: Fri, 28 Nov 2014 06:09:14 +0000
To: kde-pim
Subject: Re: [Kde-pim] kdepim-plasma
Message-Id: <2029708.bFy5QpLlv9 () serenity>
X-MARC-Message: https://marc.info/?l=kde-pim&m=141715507223771
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============5565931435321066596=="


--===============5565931435321066596==
Content-Type: multipart/signed; boundary="nextPart6473332.fIBREapisV"; micalg="pgp-sha1"; protocol="application/pgp-signature"


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

On Thursday, November 27, 2014 18.41:03 Milian Wolff wrote:
> Huh? Why would our *users* need to migrate any data when we switch ak=
onadi +
> apps from Qt4 to Qt5? The storage stays the same after all.

While Akonadi data would not migrate, there are application settings to=
=20
migrate now that the location of those has changed (at least in the ups=
tream=20
defaults). From a user's POV, they will have upgraded to the "next vers=
ion" as=20
the applications will have the new style and icons (among whatever othe=
r=20
changes come along) only to have to "upgrade again" when the new new st=
orage=20
layer appears.

My concern is that this will end up similar to how the multi-stage upgr=
ades in=20
KDEPIM4 ended up feeling.

If the time frame is reasonable, it would be nice to be able to provide=
 a one-=20
time upgrade as this will likely feel more thought-out and complete to =
the=20
user.

Another related but different thing we need to consider is data migrati=
on. At=20
the sprint, Till stated this was quite important and was not, in his op=
inion,=20
given enough attention soon enough with Akonadi and left many users unh=
appy.=20
Once the new storage layer is complete, we probably need to budget some=
 time=20
to write a migration tool.

=2D-=20
Aaron J. Seigo
--nextPart6473332.fIBREapisV
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

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

iEYEABECAAYFAlR4EY4ACgkQ1rcusafx20NyQQCeLgQB4sjAPnuCMeMXVhyomAiC
3qoAni0VeEjQFV2mKKqdOsXOxLJHLezE
=e1Rf
-----END PGP SIGNATURE-----

--nextPart6473332.fIBREapisV--


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

_______________________________________________
KDE PIM mailing list kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/
--===============5565931435321066596==--