[Gt-eos] Launching the GridCF

[Navarro, JP]

We could spin up a parallel release process with identical source at any point. This should be done earlier in 2018 to work thru spin up issues.

Once that parallel process is in place we will still need to decide whether to stay in sync for the rest 2018. The longer we can stay in sync the less effort there will be to merge upstream updates.

Perhaps we should not set a fork date until we encounter a reason to do so (such as a non-security fix that we want and Globus will not accept)?

JP


> On Oct 30, 2017, at 11:04 AM, Brian Bockelman <bbockelm at cse.unl.edu <mailto:bbockelm at cse.unl.edu>> wrote:
> 
> 
>> On Oct 30, 2017, at 10:57 AM, Navarro, JP <navarro at mcs.anl.gov <mailto:navarro at mcs.anl.gov>> wrote:
>> 
>> 
>>> On Oct 30, 2017, at 9:07 AM, Mischa Salle <msalle at nikhef.nl <mailto:msalle at nikhef.nl>> wrote:
>>> 
>>>> - Put together a timeline for a first release of the GCT.  Given we're
>>>>  working against a January 2018 deadline, I would aim to have the
>>>>  first code release be prior to that and essentially consist of the
>>>>  current fork point from the Globus Toolkit.
>>> Wouldn't it be better to make the first release just after the last
>>> globus-toolkit release?
>> 
>> Note that the Globus team will in principle released security updates throughout 2018, so we need to decide whether during 2018 we want to maintain a fork and cross port Globus’s patches or wait till the Globus team stop releasing security updates before forking.
>> 
> 
> Yeah - my thinking on this one is that it would be best to go through the "release process" prior to actually running out of time on the clock.  I assume that, for awhile, we'll have our hands full just doing the identical release as upstream.
> 
> My worst case scenario is waiting to make the first release until after the last GT release -- only to find out there is issue XYZ that we overlooked and is a blocker .
> 
> Brian
> 
> _______________________________________________
> Gt-eos mailing list
> Gt-eos at mailman.egi.eu <mailto:Gt-eos at mailman.egi.eu>
> http://mailman.egi.eu/mailman/listinfo/gt-eos

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.egi.eu/pipermail/gt-eos/attachments/20171030/2da9d601/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 873 bytes
Desc: Message signed with OpenPGP
URL: <http://mailman.egi.eu/pipermail/gt-eos/attachments/20171030/2da9d601/attachment.asc>