GLEP 2 says in section "How to Use This Template": - Replace the "GLEP: 2" header with "GLEP: XXX" since you don't yet have a GLEP number assignment. XXX is the Roman numeral for 30, so there is potential for confusion. More importantly, when rendering such a (pre-)draft GLEP with docutils-glep, I get a warning: $ glep glep-foo.rst >/dev/null glep-foo.rst:: (WARNING/2) "GLEP" header must contain an integer; "XXX" is an invalid value. In order to suppress that warning, I suggest that we recommend "9999" instead. (It is unlikely that we'll arrive at that number anytime soon; and if we do, we'll have to update our workflow anyway because of the current 4-digit file name format.) Note: PEP 1 also recommends using 9999 for drafts: https://www.python.org/dev/peps/pep-0001/#submitting-a-pep
Created attachment 527318 [details, diff] glep-0002: Recommend 9999 as number for pre-draft GLEPs.
I haven't seen any objections, therefore pushed: commit 2b2fbd8ae06fb425c6edf6b809224e31bd94c9a1 Author: Ulrich Müller <ulm@gentoo.org> Date: Sat Apr 14 11:38:37 2018 +0200 glep-0002: Recommend 9999 as number for pre-draft GLEPs. The currently used "XXX" value triggers a warning in docutils-glep. Closes: https://bugs.gentoo.org/653126
