<div dir="ltr"><div class="gmail_extra"><div><div class="gmail_signature">On Tue, May 3, 2016 at 12:24 PM, John Dickinson <span dir="ltr"><<a href="mailto:me@not.mn" target="_blank">me@not.mn</a>></span> wrote:<br></div></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">That's an interesting point. I'm not very familiar with Golang itself yet, and I haven't yet had to manage any Golang projects in prod. These sorts of questions are great!<br>
<br></blockquote><div><br></div><div>See: <a href="https://golang.org/doc/go1compat">https://golang.org/doc/go1compat</a></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
If a distro is distributing pre-compiled binaries, isn't the compatibility issue up to the distros? OpenStack is not distributing binaries (or even distro packages!), so while it's an important question, how does it affect the question of golang being an ok language in which to write openstack source code?<br></blockquote><div><br></div><div><br></div><div>I mean a commercial OpenStack distro...</div><div><br></div><div>OpenStack does not distribute binaries today (because Python is an interpreted language), but Go is a compiled language. So may be I should simplify my question -- in what form should a commercial OpenStack distro distribute OpenStack components written in Go?</div><div><br></div><div>Rayson<br><br>==================================================<br>Open Grid Scheduler - The Official Open Source Grid Engine<br><a href="http://gridscheduler.sourceforge.net/" target="_blank">http://gridscheduler.sourceforge.net/</a><br><a href="http://gridscheduler.sourceforge.net/GridEngine/GridEngineCloud.html" target="_blank">http://gridscheduler.sourceforge.net/GridEngine/GridEngineCloud.html</a><br></div><div><br></div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<span class=""><font color="#888888"><br>
--John<br>
</font></span><div class=""><div class="h5"><br>
<br>
<br>
<br>
On 3 May 2016, at 9:16, Rayson Ho wrote:<br>
<br>
> I like Go! However, Go does not offer binary compatibility between point<br>
> releases. For those who install from source it may not be a big issue, but<br>
> for commercial distributions that pre-package & pre-compile everything,<br>
> then the compiled Go libs won't be compatible with old/new releases of the<br>
> Go compiler that the user may want to install on their systems.<br>
><br>
> Rayson<br>
><br>
> ==================================================<br>
> Open Grid Scheduler - The Official Open Source Grid Engine<br>
> <a href="http://gridscheduler.sourceforge.net/" rel="noreferrer" target="_blank">http://gridscheduler.sourceforge.net/</a><br>
> <a href="http://gridscheduler.sourceforge.net/GridEngine/GridEngineCloud.html" rel="noreferrer" target="_blank">http://gridscheduler.sourceforge.net/GridEngine/GridEngineCloud.html</a><br>
><br>
><br>
><br>
><br>
> On Tue, May 3, 2016 at 11:58 AM, John Dickinson <<a href="mailto:me@not.mn">me@not.mn</a>> wrote:<br>
><br>
>> TC,<br>
>><br>
>> In reference to<br>
>> <a href="http://lists.openstack.org/pipermail/openstack-dev/2016-May/093680.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/2016-May/093680.html</a><br>
>> and Thierry's reply, I'm currently drafting a TC resolution to update<br>
>> <a href="http://governance.openstack.org/resolutions/20150901-programming-languages.html" rel="noreferrer" target="_blank">http://governance.openstack.org/resolutions/20150901-programming-languages.html</a><br>
>> to include Go as a supported language in OpenStack projects.<br>
>><br>
>> As a starting point, what would you like to see addressed in the document<br>
>> I'm drafting?<br>
>><br>
>> --John<br>
>><br>
>><br>
>><br>
>><br>
>> __________________________________________________________________________<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>><br>
>><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div><br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>