On Wed, Dec 11, 2013 at 9:29 AM, Stefan Baur <newsgroups.ma...@stefanbaur.de> wrote: > Am 11.12.2013 15:20, schrieb Mike Gabriel: > > [my test results] > >> Please send individual mails to sub...@bugs.x2go.org > > > Done, as promised. :-) > > -Stefan >
Hi Stefan, I would like to say that "I feel your pain." I agree with you that not only are 1, 2 and 3 legitimate bugs/issues with X2Go Client, but so are 4 and 5. However, as the new maintainer of the X2Go Client package for Windows, I do not believe that any of these bugs and issues are worth delaying the 4.0.1.2 release to fix. Maybe if 1,2 and 3 were regressions against 4.0.0.3, I would reconsider. However, they are existing bugs. Fortunately, the x2go bug tracker exists not just to documents bugs and how they will be fixed in future versions, but also to document workarounds for current versions. I will try to identify workarounds for you and I will post them on the bugtracker. I encourage you to do this also. Also, note that I fixed bug #230 specifically because it was easy for me to fix and because the risk of a regression is very low. All I had to edit was the NSIS script. I will need to brush up on C++ before I can fix most x2goclient bugs. -Mike DePaulo X2Go Contributor _______________________________________________ X2Go-Dev mailing list X2Go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
