[X2go-Dev] Some feature requests for x2go-client (Windows), while we're at it...

Stefan Baur newsgroups.mail2 at stefanbaur.de
Fri Dec 16 21:02:53 CET 2011


Am 16.12.2011 19:18, schrieb Heinz-M. Graesing:
> Hello Stefan,
>
> Am 16.12.2011 16:19, schrieb Stefan Baur:
>> Am 13.12.2011 08:44, schrieb Heinz-M. Graesing:
>>> Hello Stefan,
>>>
>>> Alex an I have discussed your feature request. Due to the huge
>>> amount of features implemented in the past, x2goclient has grown
>>> big and this way we are planning a rewrite of the client. This
>>> means that the accepted patch would only live until this new
>>> release and the whole work is lost.
>> :-( What's the expected release date for this new client? Are we
>> talking about a few weeks, a month, six months, a year?
> We really can't say at the moment, but this step is definitely needed.
> It will not be part of the upcoming release (baikal).

Well, don't get me wrong, I'm not trying to hurry you here.  It's just 
that if you come to the conclusion that it will be, say, at least six 
months until this new client is released, I might even decide that the 
feature is important enough for me to pay for its addition twice - once 
in the current client and once in the upcoming one.  Or maybe I'll stick 
with the current client (plus my paid-for patch) for a while, assuming 
it will still be compatible with the $NEXT_INCARNATION_AFTER_BAIKAL server.

So, is there a *minimum* time frame after the Baikal release where you 
can more or less guarantee that a new client will *not* be released, and 
old clients will continue to function with new server releases?

Kind regards,
Stefan



More information about the x2go-dev mailing list