W3C home > Mailing lists > Public > public-html@w3.org > October 2009

RE: Editor's Response in the proposed process (with particular note of spec diff links)

From: Adrian Bateman <adrianba@microsoft.com>
Date: Thu, 22 Oct 2009 03:43:15 +0000
To: Ian Hickson <ian@hixie.ch>, Maciej Stachowiak <mjs@apple.com>
CC: HTMLWG WG <public-html@w3.org>
Message-ID: <104E6B5B6535E849970CDFBB1C5216EB061F67E7@TK5EX14MBXC140.redmond.corp.microsoft.com>
On Tuesday, October 20, 2009 9:33 PM, Ian Hickson wrote:
> On Tue, 20 Oct 2009, Maciej Stachowiak wrote:
> > The other piece of information we would like in every resolved
> > bugzilla bug is a link to the relevant revision of the spec. I've
> > talked to Ian about this so far, not yet other editors. He is
> > including the bugzilla bug number in every commit. Ian tells me that,
> > given the way he edits the spec (with a long processing pipeline
> > before the change is fully committed, and often multiple edits in
> > flight), it is awkward to include a diff link in the bug at the time
> > the bug is resolved.
> 
> Actually since I started including the bug number in the commit, I just
> just made the commit script post the diff to the bug. For example:
> 
>    http://www.w3.org/Bugs/Public/show_bug.cgi?id=7416#c2
> 
> Is that ok?

Thanks Ian. This looks great and precisely addresses the concern I had. This makes it simple for bug reporters to review the changes that were made in the check-in that included the proposed resolution for their issue.

Cheers,

Adrian.
Received on Thursday, 22 October 2009 03:45:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:50 GMT