[X2Go-User] x2go-user Digest, Vol 6, Issue 19
Tom McManus
tmcmanus at nmr.mgh.harvard.edu
Tue Oct 21 15:23:52 CEST 2014
Where do I download x2goclient-4.0.1.6-20141019.dmg?
-- Tom McManus (http://help.nmr.mgh.harvard.edu)
On Tue, 21 Oct 2014 12:00pm, x2go-user-request at lists.x2go.org wrote:
> Send x2go-user mailing list submissions to
> x2go-user at lists.x2go.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.x2go.org/listinfo/x2go-user
> or, via email, send a message with subject or body 'help' to
> x2go-user-request at lists.x2go.org
>
> You can reach the person managing the list at
> x2go-user-owner at lists.x2go.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of x2go-user digest..."
>
>
> Today's Topics:
>
> 1. Changing the X2Go Client for Windows version numbering
> (Michael DePaulo)
> 2. Re: Changing the X2Go Client for Windows version numbering
> (James M. Pulver)
> 3. Re: Mac OS X 10.10 (Yosemite) X2Go client (Mike Gabriel)
> 4. Re: Mac OS X 10.10 (Yosemite) X2Go client (Ricardo D?az Mart?n)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 20 Oct 2014 08:16:21 -0400
> From: Michael DePaulo <mikedep333 at gmail.com>
> To: "x2go-user at lists.x2go.org" <x2go-user at lists.x2go.org>
> Subject: [X2Go-User] Changing the X2Go Client for Windows version
> numbering
> Message-ID:
> <CAMKht8hnGJA5+QbP-zz9QU5PUpTTMm3T-qFdqg5p-qkG_oHRNg at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> X2Go Users,
>
> I'd like feedback on this topic.
>
> I am thinking of switching the X2Go Client for Windows version
> numbering over to the version numbering that X2Go Client for Mac OS X
> uses such as:
> If X2Go Client for Windows 4.0.3.0 were released today:
> 4.0.3.0-20141020
> If I had to make any sort of change, either in the build process or in
> the source code, on 2014-11-21:
> 4.0.3.0-20141121
>
> The reason for this change is that I believe these version numbers
> will be simpler and less confusing. This would be especially true for
> Windows users who are not used to the version numbering used by Linux
> distros.
>
> Under the current version numbering , if I were to build X2Go Client
> for Windows 4.0.3.0 when it is released the version number would
> simply be:
> 4.0.3.0
> Then say I had to make 2 changes to the build process, such as calling
> different commands during the build process or bundling different 3rd
> party binaries/libraries (e.g., VcXsrv, OpenSSL). The 2 new version
> numbers would be:
> 4.0.3.0+build1
> 4.0.3.0+build2
> If I had to then make a change to the source code, it would be:
> 4.0.3.0+hotfix1
> And if I had to make 2 more changes to the build process, the 2 new
> version numbers would be:
> 4.0.3.0+hotfix1+build1
> 4.0.3.0+hotfix1+build2
>
> -Mike#2
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 20 Oct 2014 12:27:40 +0000
> From: "James M. Pulver" <jmp242 at cornell.edu>
> To: "x2go-user at lists.x2go.org" <x2go-user at lists.x2go.org>
> Subject: Re: [X2Go-User] Changing the X2Go Client for Windows version
> numbering
> Message-ID:
> <981ce53b33b44aa89d78c6107bbac2eb at BY2PR04MB775.namprd04.prod.outlook.com>
>
> Content-Type: text/plain; charset="us-ascii"
>
> Personally, I don't love either build numbering method. That said, I find the date suffix much harder to parse personally, it's too many numbers munged together and I just end up ignoring it.
>
> What do you all mean by the numbering anyway - i.e. why would
> 4.0.3.0+hotfix1
> Not be 4.0.3.1?
>
> Personally, from a Windows admin / user perspective, I don't care what the build process is in terms of a binary I download. I care if something changed.
>
> So if 4.0.3.0+build1 changed the version of gcc but didn't change the output, I doubt anyone would care - maybe somewhere would be a build # for deep debugging, but it wouldn't be in any download name someone would use.
>
> If 4.0.3.0+build2 packaged a new library that fixed a bug, I'd expect to see
> 4.0.3.1 again as it fixed something "in the product" from my perspective.
>
> I'm a fan of MajorChange.MinorFeatureChange.Bugfix.someotherchange sort of software numbering.
>
> That all said - I would like to see the numbering be consistent across platforms in terms of code that is shared, and the method also be consistent.
> --
> James Pulver
> CLASSE Computer Group
> Cornell University
>
>
> -----Original Message-----
> From: x2go-user-bounces at lists.x2go.org [mailto:x2go-user-bounces at lists.x2go.org] On Behalf Of Michael DePaulo
> Sent: Monday, October 20, 2014 8:16 AM
> To: x2go-user at lists.x2go.org
> Subject: [X2Go-User] Changing the X2Go Client for Windows version numbering
>
> X2Go Users,
>
> I'd like feedback on this topic.
>
> I am thinking of switching the X2Go Client for Windows version numbering over to the version numbering that X2Go Client for Mac OS X uses such as:
> If X2Go Client for Windows 4.0.3.0 were released today:
> 4.0.3.0-20141020
> If I had to make any sort of change, either in the build process or in the source code, on 2014-11-21:
> 4.0.3.0-20141121
>
> The reason for this change is that I believe these version numbers will be simpler and less confusing. This would be especially true for Windows users who are not used to the version numbering used by Linux distros.
>
> Under the current version numbering , if I were to build X2Go Client for Windows 4.0.3.0 when it is released the version number would simply be:
> 4.0.3.0
> Then say I had to make 2 changes to the build process, such as calling different commands during the build process or bundling different 3rd party binaries/libraries (e.g., VcXsrv, OpenSSL). The 2 new version numbers would be:
> 4.0.3.0+build1
> 4.0.3.0+build2
> If I had to then make a change to the source code, it would be:
> 4.0.3.0+hotfix1
> And if I had to make 2 more changes to the build process, the 2 new version numbers would be:
> 4.0.3.0+hotfix1+build1
> 4.0.3.0+hotfix1+build2
>
> -Mike#2
> _______________________________________________
> x2go-user mailing list
> x2go-user at lists.x2go.org
> http://lists.x2go.org/listinfo/x2go-user
>
>
> ------------------------------
>
> Message: 3
> Date: Tue, 21 Oct 2014 07:29:27 +0000
> From: Mike Gabriel <mike.gabriel at das-netzwerkteam.de>
> To: Ricardo D?az Mart?n <ricardo.diaz at oceanosoft.com>
> Cc: x2go-user at lists.x2go.org
> Subject: Re: [X2Go-User] Mac OS X 10.10 (Yosemite) X2Go client
> Message-ID:
> <20141021072927.Horde.2ismKJ5MkdR9q5FJX70Shw1 at mail.das-netzwerkteam.de>
>
> Content-Type: text/plain; charset="utf-8"; Format="flowed";
> DelSp="Yes"
>
> Hi Ricardo,
>
> On Di 21 Okt 2014 07:54:51 CEST, Ricardo D?az Mart?n wrote:
>
>> Hi Mike,
>>
>> I got some users updated to Yosemite. Could you send to me or upload to the
>> releases the .dmg Yosemite compatible.
>>
>> Regards,
>>
>> --
>> <ricardo.diaz at oceanosoft.com>
>
> The Yosemite fix is now available in x2goclient-4.0.1.6-20141019.dmg [1].
>
> Sorry for the delay!
> Mike
>
> [1]
> http://code.x2go.org/releases/binary-macosx/x2goclient/releases/4.0.2.1/x2goclient-4.0.2.1-20141019.dmg
>
> --
>
> DAS-NETZWERKTEAM
> mike gabriel, herweg 7, 24357 fleckeby
> fon: +49 (1520) 1976 148
>
> GnuPG Key ID 0x25771B31
> mail: mike.gabriel at das-netzwerkteam.de, http://das-netzwerkteam.de
>
> freeBusy:
> https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 819 bytes
> Desc: Digitale PGP-Signatur
> URL: <http://lists.x2go.org/pipermail/x2go-user/attachments/20141021/3171c21b/attachment-0001.pgp>
>
> ------------------------------
>
> Message: 4
> Date: Tue, 21 Oct 2014 11:11:51 +0200
> From: Ricardo D?az Mart?n <ricardo.diaz at oceanosoft.com>
> To: Mike Gabriel <mike.gabriel at das-netzwerkteam.de>
> Cc: "x2go-user at lists.x2go.org" <x2go-user at lists.x2go.org>
> Subject: Re: [X2Go-User] Mac OS X 10.10 (Yosemite) X2Go client
> Message-ID:
> <CAPWth0J3gGAtRik0xGD4D7jD8M3pkjZv2+GfqHLhQa9Jdzmoow at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Thanks Mike!
>
> Everything is working again.
>
> Cheers,
> Ricardo
>
>
> --
>
>
> 2014-10-21 9:29 GMT+02:00 Mike Gabriel <mike.gabriel at das-netzwerkteam.de>:
>
>> Hi Ricardo,
>>
>>
>> On Di 21 Okt 2014 07:54:51 CEST, Ricardo D?az Mart?n wrote:
>>
>> Hi Mike,
>>>
>>> I got some users updated to Yosemite. Could you send to me or upload to
>>> the
>>> releases the .dmg Yosemite compatible.
>>>
>>> Regards,
>>>
>>> --
>>> <ricardo.diaz at oceanosoft.com>
>>>
>>
>> The Yosemite fix is now available in x2goclient-4.0.1.6-20141019.dmg [1].
>>
>> Sorry for the delay!
>> Mike
>>
>> [1] http://code.x2go.org/releases/binary-macosx/x2goclient/
>> releases/4.0.2.1/x2goclient-4.0.2.1-20141019.dmg
>>
>> --
>>
>> DAS-NETZWERKTEAM
>> mike gabriel, herweg 7, 24357 fleckeby
>> fon: +49 (1520) 1976 148
>>
>> GnuPG Key ID 0x25771B31
>> mail: mike.gabriel at das-netzwerkteam.de, http://das-netzwerkteam.de
>>
>> freeBusy:
>> https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-
>> netzwerkteam.de.xfb
>>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.x2go.org/pipermail/x2go-user/attachments/20141021/a4838bf9/attachment-0001.html>
>
> ------------------------------
>
> _______________________________________________
> x2go-user mailing list
> x2go-user at lists.x2go.org
> http://lists.x2go.org/listinfo/x2go-user
>
> End of x2go-user Digest, Vol 6, Issue 19
> ****************************************
>
>
>
The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.
More information about the x2go-user
mailing list