<div dir="ltr"><span class="im" style="font-size:12.8px"><blockquote style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex" class="gmail_quote">> well, if you look up in the thread, a few of us are saying it's not. It doesn't distinguish Current Specs vs Proposals very well.<br></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"> </blockquote><blockquote style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex" class="gmail_quote">How would you add that metadata to the version string (according to PEP 440)? Semver 3.0 (pbr)<br><font color="#3e4349" face="Arial, sans-serif"><span style="font-size:14.4px;line-height:21.6px">From <a href="http://docs.openstack.org/developer/pbr/semver.html" target="_blank">http://docs.openstack.org/developer/pbr/semver.html</a> :<br></span></font><span style="font-size:12.8px"> Example: 1.0.0.dev8 < 1.0.0.dev9 < 1.0.0.a1.dev3 < 1.0.0.a1 < 1.0.0.b2 < 1.0.0.c1 < 1.0.0</span></blockquote><div><br></div><div> </div></span><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Sep 7, 2015 at 1:13 PM, Marcus Smith <span dir="ltr"><<a href="mailto:qwcode@gmail.com" target="_blank">qwcode@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">pulling this idea out of the "Linux wheel support" thread, since it deserves it's own thread...<div><br></div><div>the idea being that we should better distinguish:</div><div>1) the current packaging "Specs" (for metadata, versions, etc...)</div><div>vs</div><div>2) Proposals to change them</div><div><br></div><div>currently, we just have PEPs that serve both roles.</div><div><br></div><div>so the idea would be to:</div><div>1) house current specs at packaging.python.org... basically a document tree that's organized by topic, not numbers and it's free of proposal rationales, historical discussion, and transition plans etc...</div></div></blockquote><div><br></div><div>* <a href="https://packaging.python.org/en/latest/glossary.html#term-version-specifier">https://packaging.python.org/en/latest/glossary.html#term-version-specifier</a> -> <a href="http://pypa.io/en/latest/peps">pypa.io/en/latest/peps</a></div><div>* <a href="https://www.pypa.io/en/latest/peps">https://www.pypa.io/en/latest/peps</a><br></div><div>* <a href="https://github.com/pypa/pypa.io/blob/master/source/peps.rst">https://github.com/pypa/pypa.io/blob/master/source/peps.rst</a></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div>2) keep using the PEP process for adjusting or adding to the specs</div><div><div><br></div></div><div>and assuming that approach, I raised a few "publishing" questions:</div><div>1) do we publish/render all supported versions of a certain spec, or just the latest</div><div>2) if we publish them all, then how? do we maintain separate documents for distinct versions? if not, how do we do it?</div></div></blockquote><div><br></div><div>Tagged [semver 3.0 (+1)] versions can be managed *individually* with readthedocs.</div><div><br></div><div>One old-school way to do this would be to e.g. write a conf.py and a sphinx adapter for PEPs: <a href="https://github.com/python/peps">https://github.com/python/peps</a></div><div><br></div><div>And copy/paste with version strings at the end of filenames</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><span class=""><font color="#888888"><div><br></div><div>--Marcus</div><div><br></div><div><br></div></font></span></div>
<br>_______________________________________________<br>
Distutils-SIG maillist - <a href="mailto:Distutils-SIG@python.org">Distutils-SIG@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/distutils-sig" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/distutils-sig</a><br>
<br></blockquote></div><br></div></div>