<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">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.<div class=""><br class=""></div><div class="">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.</div><div class=""><br class=""></div><div class="">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)?</div><div class=""><br class=""></div><div class="">JP</div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Oct 30, 2017, at 11:04 AM, Brian Bockelman <<a href="mailto:bbockelm@cse.unl.edu" class="">bbockelm@cse.unl.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Oct 30, 2017, at 10:57 AM, Navarro, JP <<a href="mailto:navarro@mcs.anl.gov" class="">navarro@mcs.anl.gov</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Oct 30, 2017, at 9:07 AM, Mischa Salle <<a href="mailto:msalle@nikhef.nl" class="">msalle@nikhef.nl</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><blockquote type="cite" style="font-family: Menlo-Regular; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">- Put together a timeline for a first release of the GCT. Given we're<br class=""> working against a January 2018 deadline, I would aim to have the<br class=""> first code release be prior to that and essentially consist of the<br class=""> current fork point from the Globus Toolkit.<br class=""></blockquote><span style="font-family: Menlo-Regular; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Wouldn't it be better to make the first release just after the last</span><br style="font-family: Menlo-Regular; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Menlo-Regular; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">globus-toolkit release?</span><br style="font-family: Menlo-Regular; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""></div></div></blockquote></div><br class=""><div class="">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.</div><div class=""><br class=""></div></div></div></blockquote><div class=""><br class=""></div><div class="">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.</div><div class=""><br class=""></div><div class="">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 .</div><div class=""><br class=""></div></div>Brian<div class=""><br class=""></div></div>_______________________________________________<br class="">Gt-eos mailing list<br class=""><a href="mailto:Gt-eos@mailman.egi.eu" class="">Gt-eos@mailman.egi.eu</a><br class=""><a href="http://mailman.egi.eu/mailman/listinfo/gt-eos" class="">http://mailman.egi.eu/mailman/listinfo/gt-eos</a><br class=""></div></blockquote></div><br class=""></div></body></html>