This strict freeze policy has been decided by Tarek.  The less work there is on distutils’ side, the less synchronization we’ll have to do in distutils2.  We do fix doc bugs, we can also fix markup or add links, but that’s it.  Improving docs is for distutils2.

Note that at first I wanted to improve distutils docs even though the code was frozen, but I now agree with Tarek that it would take up a lot of time that is better spent in distutils2.  (Regarding the options parameter, a Montreal-Python contributor added a test for it and a TODO note about lack of documentation.  See, things get better one step at a time :)

I hope this answers your question without sounding too dictatorial.  I understand your viewpoint but ultimately agree with the freeze.