Workflow for provinding win32 X2Go Client builds (was: Re: [X2Go-User] x2goclient 4.0.1.0 for windows is available)
Hi Alex, hi all,
(grabbing this thread and moving it over to x2go-dev ML...)
On Do 31 Jan 2013 15:16:45 CET Oleksandr Shneyder wrote:
http://code.x2go.org/releases/binary-win32/x2goclient/x2goclient-4.0.1.0-pre...
IMHO we need to change something about the way we (you) provide the
Windows builds.
The currently available binary builds of X2Go Client are these:
x2goclient-3.99.0.0-setup.exe x2goclient-3.99.0.1-setup.exe x2goclient-3.99.0.2-setup.exe x2goclient-3.99.0.3-setup.exe x2goclient-3.99.0.4-setup.exe x2goclient-3.99.0.5-setup.exe x2goclient-3.99.1.0-setup.exe x2goclient-3.99.1.1-setup.exe x2goclient-3.99.2.1-setup.exe x2goclient-3.99.3.0-pre1-setup.exe x2goclient-3.99.3.0-pre2-setup.exe x2goclient-3.99.3.0-pre3-setup.exe x2goclient-3.99.3.1-pre1-setup.exe x2goclient-4.0.1.0-pre1-setup.exe
As you see, for the recent releases of X2Go Client, there have not
been any builds. The builds have been taken prior to the release from
some version in Git, that we now cannot reference anymore.
Such a way of distributing X2Go Client creates problems concerning
compliance with the GPL. For each binary build of X2Go Client we have
to be able to make a reference (easily) to the source code used for
building X2Go Client.
With the Windows builds of X2Go Client, the current situation does not
match GPL, we have to improve that!!!
My suggestion for a more versatile workflow of providing X2Go Client
builds for Windows is this...
Preview build of X2Go Client:
(a) provide preview builds that have the Git commit hash in its file name, normally it is sufficient to give the first 7 digits of the Git commit hash. If 7 digits is not enough for an unequivocal match, one has to use more than 7 digits...
Use »git log <7-digits-of-hash>« to see if the abbreviated commit hash
is long enough.(b) create checksums+signature (md5, sha1, GnuPG) for the preview build (use [2] to do this). (c) upload the built .exe file and the signature/checksums to code.x2go.org
Stable releases of X2Go Client:
(a) on source tarball release, build X2Go Client against that tarball (b) create checksums+signature for that (again using [2]) (c) upload the stable build of X2Go Client to code.x2go.org (d) release all preview builds for that version, including their checksums/signatures
[1] http://code.x2go.org/releases/source/x2goclient [2] http://code.x2go.org/gitweb?p=buildscripts.git;a=blob;f=bin/signtarballs
Requesting comment / feedback on this!!!
It may also be an idea to delegate the X2Go Client builds on Windows
to someone else in the project, to take that bit of workload off of
you. But for that, it would need a howto on the wiki that explains the
way X2Go Client has to be built+assembled on Windows.
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On Fr 01 Feb 2013 11:14:42 CET Mike Gabriel wrote:
(d) release all preview builds for that version, including their checksums/signatures
Ooops... typo. Should have been: _remove_ all preview builds...
Mike
--
DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On 2013-02-01 11:14, Mike Gabriel wrote:
Preview build of X2Go Client:
(a) provide preview builds that have the Git commit hash in its file name, normally it is sufficient to give the first 7 digits of the Git commit hash. If 7 digits is not enough for an unequivocal match, one has to use more than 7 digits...
I think it's better adding a file Git-rev containing the GIT-Version. It's way easier to get the latest version using rc1, rc2, etc
(d) remove all preview builds for that version, including their checksums/signatures
I don't think there is a good reason for doing so. Especially as there might be regressions, etc.
Cheers Morty
-- Dipl.-Ing. Moritz 'Morty' Struebe (Wissenschaftlicher Mitarbeiter) Lehrstuhl für Informatik 4 (Verteilte Systeme und Betriebssysteme) Friedrich-Alexander-Universität Erlangen-Nürnberg Martensstr. 1 91058 Erlangen
Tel : +49 9131 85-25419 Fax : +49 9131 85-28732 eMail : struebe@informatik.uni-erlangen.de WWW : http://www4.informatik.uni-erlangen.de/~morty
Am 01.02.2013 12:54, schrieb Moritz Struebe:
(d) remove all preview builds for that version, including their checksums/signaturesI don't think there is a good reason for doing so. Especially as there might be regressions, etc.
+1
Tagging them as preview and moving them to a different folder is enough; you should not remove them from the download area.
-Stefan
Am 01.02.2013 12:54, schrieb Moritz Struebe:
On 2013-02-01 11:14, Mike Gabriel wrote:
Preview build of X2Go Client:
(a) provide preview builds that have the Git commit hash in its file name, normally it is sufficient to give the first 7 digits of the Git commit hash. If 7 digits is not enough for an unequivocal match, one has to use more than 7 digits...
I think it's better adding a file Git-rev containing the GIT-Version. It's way easier to get the latest version using rc1, rc2, etc
okay, it is a good point. I would add to every a file with name like: x2goclient-3.99.3.1-pre1-setup.exe.git and in that file url to commit.
(d) remove all preview builds for that version, including their checksums/signaturesI don't think there is a good reason for doing so. Especially as there might be regressions, etc.
It's a good point too. But I think, if we will keep all this versions, it will bee too much files in the same directory. What do you think about creating special directory for previews ?
regards alex
Cheers Morty
X2Go-Dev mailing list X2Go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
-- Oleksandr Shneyder Dipl. Informatik X2go Core Developer Team
email: oleksandr.shneyder@obviously-nice.de web: www.obviously-nice.de
--> X2go - everywhere@home
Am 01.02.2013 13:04, schrieb Oleksandr Shneyder:
[......]
It's a good point too. But I think, if we will keep all this versions, it will bee too much files in the same directory. What do you think about creating special directory for previews ?
I would also create folder for every version, something like:
x2goclient releases 4.0.0.1 x2goclient-4.0.0.1-setup.exe x2goclient-4.0.0.1-setup.exe.asc x2goclient-4.0.0.1-setup.exe.md5 x2goclient-4.0.0.1-setup.exe.sha1 previews 4.0.1.0 x2goclient-4.0.0.1-rc1-setup.exe x2goclient-4.0.0.1-rc1-setup.exe.asc x2goclient-4.0.0.1-rc1-setup.exe.md5 x2goclient-4.0.0.1-rc1-setup.exe.sha1 x2goclient-4.0.0.1-rc1-setup.exe.git
what do you think?
regards alex
[.......]
Oleksandr Shneyder Dipl. Informatik X2go Core Developer Team
email: oleksandr.shneyder@obviously-nice.de web: www.obviously-nice.de
--> X2go - everywhere@home
Hi Alex,
On Fr 01 Feb 2013 13:14:17 CET Oleksandr Shneyder wrote:
Am 01.02.2013 13:04, schrieb Oleksandr Shneyder:
[......]
It's a good point too. But I think, if we will keep all this versions, it will bee too much files in the same directory. What do you think about creating special directory for previews ?
I would also create folder for every version, something like:
x2goclient releases 4.0.0.1 x2goclient-4.0.0.1-setup.exe x2goclient-4.0.0.1-setup.exe.asc x2goclient-4.0.0.1-setup.exe.md5 x2goclient-4.0.0.1-setup.exe.sha1 previews 4.0.1.0 x2goclient-4.0.0.1-rc1-setup.exe x2goclient-4.0.0.1-rc1-setup.exe.asc x2goclient-4.0.0.1-rc1-setup.exe.md5 x2goclient-4.0.0.1-rc1-setup.exe.sha1 x2goclient-4.0.0.1-rc1-setup.exe.git
what do you think?
regards alex
[.......]
Great that you reacted so promptly on this!!! Good work from what I
have seen!!!
Mike
--
DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
-
Mike Gabriel -
Moritz Struebe -
Oleksandr Shneyder -
Stefan Baur