<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Mattias,<br>
<br>
Thanks for pinging this thread. I vote 6.2.<br>
<br>
- Brian<br>
<br>
<div class="moz-cite-prefix">On 11/2/18 8:07 AM, Frank Scheiner via Gt-eos wrote:<br>
</div>
<blockquote type="cite" cite="mid:82a03622-4a55-f9ce-51cb-75f9e064f1fe@hlrs.de">Hi Mattias, all,
<br>
<br>
On 11/2/18 12:50, Mattias Ellert via Gt-eos wrote: <br>
<blockquote type="cite">Hi! <br>
<br>
Can we come to some kind of decision? I would like to package the <br>
changes made to the sources since the last tag, and the way it is set <br>
up now source tarballs are not created unless there is a tag. If it <br>
drags out for a long time I could make package updates using patches, <br>
but I think we can avoid that. <br>
<br>
Regarding the toolkit version number: It should be 6.something - <br>
otherwise the <a class="moz-txt-link-freetext" href="https://repo.gridcf.org/gct6/sources/">
https://repo.gridcf.org/gct6/sources/</a> address no longer <br>
makes sense and we would have to do quite a lot of changes. <br>
<br>
The number 6.0 appears in a few places in the packaging files, so if we <br>
stick to that no changes are needed. If we choose 6.1 or 6.2, a few <br>
changes are needed, but it would be manageable (those changes should be <br>
done before tagging though). <br>
</blockquote>
<br>
I'm ok with both 6.0 and 6.2. But my preference would be 6.2 actually, although we could still postpone 6.2 until after end of 2018 and stay with 6.0 for now.
<br>
<br>
So your decision. <br>
<br>
Cheers, <br>
Frank <br>
<br>
<blockquote type="cite"><br>
Mattias <br>
<br>
mån 2018-10-22 klockan 10:12 -0500 skrev Mátyás Selmeci via Gt-eos: <br>
<blockquote type="cite">Hi Mischa and folks, <br>
<br>
I _really_ do not want to go backwards in versions. I'm sure people <br>
have scripts that check for $GLOBUS_VERSION and do one thing if it's <br>
<blockquote type="cite">= 6.0 and another if it's < 6.0. I don't want to mess up those scripts.
<br>
</blockquote>
<br>
We don't have to worry about conflicting with a Globus 6.1 or 6.2 <br>
release because: <br>
<br>
1. We've been updating our repo to keep up with their repo. If they <br>
make a 6.2, then our 6.2 will incorporate their changes. <br>
<br>
2. They've been on 6.0 since _2014_. They haven't bumped the version <br>
even when they added features. Now they're in bugfix-only mode so <br>
they won't be adding features either. <br>
<br>
3. We can ask the Globus developers if they're OK with us calling our <br>
version 6.2. <br>
<br>
Thanks, <br>
-Mat <br>
<br>
<br>
-------- Original Message -------- <br>
From: Mischa Salle <br>
Sent: Sun, Oct 21, 2018 4:04 AM CDT <br>
Subject: [Gt-eos] ready to tag <br>
<br>
Hi all, <br>
<br>
We have a few options each with pros and cons: <br>
- 6.1 is logical, but used to indicate development version (see <br>
<a class="moz-txt-link-freetext" href="http://toolkit.globus.org/toolkit/downloads/">
http://toolkit.globus.org/toolkit/downloads/</a> <br>
We don't have to keep to that schema (Linux kernel also dropped it), <br>
but it could be confusing. <br>
- 6.2 is then more logical, but both still have the problem that there <br>
is indeed a small chance that Globus will still release something, a <br>
final release or so (although I very much doubt that). OTOH, we're <br>
called gct, not globus_toolkit, so I personally think 6.something <br>
should be fine. <br>
- 1.0 has none of the above problems, we can also decide then to <br>
continue with 1.1 as the next stable (minor)release. Problem is that <br>
we have already a gct-6.0.1536386276 as a prerelease. <br>
Ideally I think Globus shouldn't have been using 6.0.XXXX as a <br>
prerelease but something like 6.0.0-XXXX, which works better with a sort <br>
and is consistent with typical debian and rpm numbering. <br>
<br>
I think I personally would prefer to move to a gct-1.0.0 combined from <br>
now on with 1.0.0-$(date +%s) for the development releases. <br>
<br>
Cheers, <br>
Mischa <br>
<br>
<br>
On Fri, Oct 19, 2018 at 06:13:16PM +0200, End of Support of Globus <br>
Toolkit wrote: <br>
<blockquote type="cite">Hi all, <br>
<br>
<blockquote type="cite">Now that Mattias has made EPEL and Debian packages from the current
<br>
builds, I think we're finally ready to tag a release. Does anybody have <br>
an objection to the version 6.0.1? I'd like to keep the "6.0" for now to <br>
emphasize that we're still compatible with that version of the Globus <br>
Toolkit. <br>
</blockquote>
<br>
Will there be a Globus 6.1 or 7.0 at some point, that some of our customers <br>
could be exposed to? If so, it would lead to confusion sooner or later. <br>
<br>
Should we better start our releases with 1.0.0 instead and mention desired <br>
compatibility details in the release notes? <br>
</blockquote>
<br>
On Fri, Oct 19, 2018 at 11:34:27AM -0500, End of Support of Globus <br>
Toolkit wrote: <br>
<blockquote type="cite">Sorry, looks like we might not be able to use 6.0.1 because the "micro"
<br>
version number is actually the timestamp of the latest commit, which <br>
gets added to the version of the "gct" tarball. <br>
<br>
The version "6.0" gets embedded in several places in the code, most <br>
notably as the GLOBUS_VERSION environment variable and the script <br>
"/usr/bin/globus-version", so we'll have to try out 6.1 first to make <br>
sure it doesn't cause any problems. <br>
<br>
-Mat <br>
<br>
-------- Original Message -------- <br>
From: Mátyás Selmeci <br>
Sent: Fri, Oct 19, 2018 10:53 AM CDT <br>
Subject: ready to tag <br>
<br>
Hi all, <br>
<br>
Now that Mattias has made EPEL and Debian packages from the current <br>
builds, I think we're finally ready to tag a release. Does anybody have <br>
an objection to the version 6.0.1? I'd like to keep the "6.0" for now to <br>
emphasize that we're still compatible with that version of the Globus <br>
Toolkit. <br>
<br>
Thanks, <br>
-Mat <br>
<br>
<br>
<br>
</blockquote>
<br>
<br>
<blockquote type="cite">_______________________________________________ <br>
Gt-eos mailing list <br>
<a class="moz-txt-link-abbreviated" href="mailto:Gt-eos@mailman.egi.eu">Gt-eos@mailman.egi.eu</a>
<br>
<a class="moz-txt-link-freetext" href="http://mailman.egi.eu/mailman/listinfo/gt-eos">http://mailman.egi.eu/mailman/listinfo/gt-eos</a>
<br>
</blockquote>
<br>
<br>
<br>
<br>
_______________________________________________ <br>
Gt-eos mailing list <br>
<a class="moz-txt-link-abbreviated" href="mailto:Gt-eos@mailman.egi.eu">Gt-eos@mailman.egi.eu</a>
<br>
<a class="moz-txt-link-freetext" href="http://mailman.egi.eu/mailman/listinfo/gt-eos">http://mailman.egi.eu/mailman/listinfo/gt-eos</a>
<br>
</blockquote>
<br>
<br>
_______________________________________________ <br>
Gt-eos mailing list <br>
<a class="moz-txt-link-abbreviated" href="mailto:Gt-eos@mailman.egi.eu">Gt-eos@mailman.egi.eu</a>
<br>
<a class="moz-txt-link-freetext" href="http://mailman.egi.eu/mailman/listinfo/gt-eos">http://mailman.egi.eu/mailman/listinfo/gt-eos</a>
<br>
<br>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Gt-eos mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gt-eos@mailman.egi.eu">Gt-eos@mailman.egi.eu</a>
<a class="moz-txt-link-freetext" href="http://mailman.egi.eu/mailman/listinfo/gt-eos">http://mailman.egi.eu/mailman/listinfo/gt-eos</a>
</pre>
</blockquote>
<br>
</body>
</html>