[X2Go-Dev] Bug#891: I have a fix for VcXsrv, but it needs discussion

[Stefan Baur]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Am 28.06.2015 um 02:54 schrieb Michael DePaulo:
> However, If I release X2Go Client 4.0.4.1 (or an update to
> 4.0.4.0) with this fix, then sessions started on X2Go Client for
> Windows 4.0.4.0-2015.06.24 and earlier can not be resumed on the
> new version. This could be very disruptive to users.
> 
> Does anyone have any thoughts on this dilemma?

Don't we have the x.x.x.x versioning scheme for such reasons?
Bump the version number up in a position that indicates "things may
break" and all should be good, no?

Or could you create a patch that allows toggling between the two modes
of operation, and when the first reconnect fails, try it with the
other mode?

- -Stefan

- -- 
BAUR-ITCS UG (haftungsbeschränkt)
Geschäftsführer: Stefan Baur
Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364
Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJVj7oZAAoJEG7d9BjNvlEZSXMH/iXBTzzP8txVG/K1lKPpKOeX
nBO/emM8rdSXFcTOi4u1cX3cTaVbW+gDN8VzxXhTv9kG1B/2GoYdozmjcMQT9y3K
QBF2ufkQwFzrxG8+v8K9liVFfplyaCoBHskK8tLBEsDhl0fJbHtIJ39KM2CzOpz8
tlPsUO/oAZkghkFLDQQ28iT34mVspRS7n7L7c6+Cg2OBS8XFs+SLJf4I1NbHua2H
1ccRR+fkWb6tfy0khOrB6l4+XzfKV6CgY31y3hhCL6L1Zc8VyUOHqSe6qX/su09A
/ZmMXDvMih5x1UjI4qsIv3DLKvPc+Iqxg3GyXcUnyBUVwmj6YhZHZO9CKKJzqQs=
=SoQX
-----END PGP SIGNATURE-----