6 | | * Python versions: we support Python 2.4 to 2.7 (ie: CentOS5.x for old versions of python) - code that is not backwards compatible can sometimes make it into the repository (ie python syntax: r2616, r2615, r2608, r1280, r991, r990), simply compile-testing it is often enough to spot those, other issues may affect packaging (ie: #116) which means testing beta package builds, other bugs can be more difficult to identify and even more difficult to fix (ie: #251, #215). We also want to check that the Python 3.x version can be built (compile tested), though actually using/testing it is not required at present since it isn't officially supported. |
7 | | * gtk/pygtk versions: similar to Python, older versions (ie: 2.17 and older) can sometimes cause problems (ie: r1498, r555, r554). |
| 6 | * Python versions: we support Python 2.4 to 2.7 (ie: CentOS5.x for old versions of python) - code that is not backwards compatible can sometimes make it into the repository (ie python syntax: r2616, r2615, r2608, r1280, r991, r990), simply compile-testing it is often enough to spot those, other issues may affect packaging (ie: #116) which means testing beta package builds, other bugs can be more difficult to identify and even more difficult to fix (ie: #251, #215). We also want to check that the Python 3.x version can be built via the [ https://www.xpra.org/trac/browser/trunk/src/python3-build python3-build] script (compile tested), though actually using/testing it is not required at present since it isn't officially supported. |
| 7 | * gtk/pygtk versions: similar to Python, older versions (ie: 2.17 and older) can cause problems, see: r1498, r555, r554. |
8 | 8 | * client applications: it is important to test a wide range of client applications, using a wide variety of UI toolkits and languages: gtk, qt/kde, wx, Java (see #162), etc.. Each can uncover subtle bugs. Then there are specific applications that are known to cause problems because of the way the interact with the X11 server: wine applications?, VMWare? (#199), Firefox? (#220, #158, #96), etc. Also, newer versions of specific target applications may change the behaviour of the application in ways which have a significant impact on xpra compression/quality. |
9 | 9 | * backwards compatibility with old versions: we try to keep backwards compatibility with older versions as much as possible, though some features may not be available. Occasionally we will drop compatibility (ie: #57) to allow the code to move on from old crufty workarounds. At present, all versions from 0.3.11 onwards should be able to connect, both as client and server. |
10 | 10 | * unusual setups: although these may not be optimal, people still expect this to work - and it should! Again, the errors that this uncovers may well help in other areas. Things like: running xpra nested (#210), running xpra from "{{{ssh -X}}}" / "{{{ssh -Y}}}" (#207, #3) |
11 | 11 | * platform specific quirks: OSX problems (#249), platforms with static builds of the x264 and vpx libraries or those where the dynamic libraries are bundled in a binary image (#103): MS Windows, OSX, CentOS 5.x, CentOS 6.x, Debian Squeeze, Ubuntu Lucid) |