On 2010-02-27 04:46 William Allen Simpson said the following:
You are incorrect. Get off your high horse. You should have notified the
secretariat of the version change weeks ago.
Below is the response from Glen at the secretariat staff to my notification
of the version change, which *was* sent weeks ago, on February 4th. The new
version *has* been installed for the automated submission tool (I verified
that yesterday before answering your first mail) but clearly there's an older
copy somewhere else in their system.
Your assumption of what I haven't done but should have done is incorrect.
Your initial 'bugreport' contained no specifics whatsoever.
You inappropriately sent the 'tool is broken' message to the whole IETF
general discussion list, in addition to addressing me directly (so it's
not as if you didn't know where to direct a bug report).
All of the above earns you no respect with me, and that colours my
responses. Next time, send a bug report to the secretariat or to me
directly, containing specifics that lets us *fix* the problem, rather
than blazoning an unspecific and unhelpful 'Things don't work' message
across the sky, and you might get a different tone back.
On 2010-02-04 20:09 Glen said the following:
On 2/4/2010 3:31 AM, Henrik Levkowetz wrote:
This is an automatic notification about a new idnits version, v2.12.01,
generated when doing 'make upload' for idnits.
* The order of final double-quote and sentence stop in the ID-guidelines
paragraph 5 text differed between the idnits expectations and the
web page. Changed to accept both.
* The ID-guidelines document combines the trust-specified statement of
conformance with BCP 78 and 79 with the following statement of drafts
being working documents into one paragraph, while idnits only would
recognize them as separate paragraphs. Fixed to accept both.
* Idnits expected the final URL in the ID-guidelines section 5 para 7
to end in a slash, while the guidelines specifies it without slash.
Changed to accept both.
The new version is available for download here:
Ietf mailing list