Hi guys,
I've started investigating or working on multiple tasks, but never finished them.
These are going to be my priorities for the next few months:
Fixing any major bugs/regressions in X2Go Client for Windows before we release 4.0.3.0 (due next month probably.)
Providing any security fixes for 3rd party components in X2Go Client for Windows.
Getting any GNOME3 compatibility fixes/packages into Debian 8 Jessie, Ubuntu 14.10 Utopic Unicorn, and Fedora 21. I will prioritize those distros in that order.
Adding support for new desktop environments in X2Go before we release X2Go Client 4.0.3.0. (See this email thread.) http://lists.x2go.org/pipermail/x2go-dev/2014-August/007929.html
Upstreaming the Pageant support patch for libssh 0.6.x (see bug: #590).
-Mike#2
Am 07.09.2014 um 17:42 schrieb Michael DePaulo:
- Fixing any major bugs/regressions in X2Go Client for Windows before we release 4.0.3.0 (due next month probably.)
[...]
- Adding support for new desktop environments in X2Go before we release X2Go Client 4.0.3.0. (See this email thread.) http://lists.x2go.org/pipermail/x2go-dev/2014-August/007929.html
#4 might collide with #1. Are you sure you don't want to do #4 for a 4.0.3.x or 4.0.4.x release instead?
-Stefan
On Sun, Sep 7, 2014 at 11:44 AM, Stefan Baur <x2go-ml-1@baur-itcs.de> wrote:
Am 07.09.2014 um 17:42 schrieb Michael DePaulo:
- Fixing any major bugs/regressions in X2Go Client for Windows before we release 4.0.3.0 (due next month probably.)
[...]
- Adding support for new desktop environments in X2Go before we release X2Go Client 4.0.3.0. (See this email thread.) http://lists.x2go.org/pipermail/x2go-dev/2014-August/007929.html
#4 might collide with #1. Are you sure you don't want to do #4 for a 4.0.3.x or 4.0.4.x release instead?
I should have mentioned #1:
As a high priority, I will focus only on desktop environments which already work, but you have to specify the command manually. For example, IceWM and OpenBox. Any desktop environments which require non-trivial workarounds (such as Enlightenment, whose bug #555 seems to be non-trivial to fix) will be a low priority for me.
I believe we should add new features like this during a 4.0.x.0 release rather than a 4.0.x.y release.
-Mike#2