bugs2html is an XSLT 2.0 stylesheet bugs2html.xsl and a separate set of entities bugs2html-specinfo.dtd for generating a simple disposition of comments out of Bugzilla. The output provides just enough information for a transition call, but not more. The benefit is that the process is mostly automated, and it takes not much time to set it up.
NOTE: You need appropriate access rights to Bugzilla for the following steps. Talk to your W3C staff contact or me for more information.
Add
button.
Your product will now be listed at
http://www.w3.org/Bugs/Public/editproducts.cgi.Edit product...
column. You will be directed to a page like http://www.w3.org/Bugs/Public/editproducts.cgi?action=edit&product=myProduct.Edit components
and on the
following page Add a new component ...
(and repeat these
steps for each deliverable you want to track via Bugzilla.). Enter the
name of the component (normally one of the deliverables your WG is
working on), the description and the default assignee (e.g. the mail
address of the WG chair or staff contact). The default QA contact is
optional and can be set e.g. to a mailing list you want to use for
notification of new bugs and bug changes.Last Call
), you should add versions to your product. You can
do that starting at e.g. http://www.w3.org/Bugs/Public/editversions.cgi?product=myProduct
by clicking on Edit versions
.Edit milestones
.DOCTYPE
from the XML document. You
can see a sample XML document here.specTitle
(the title of your specification)specPubDate
(the publication date)specStatus
(the status (e.g. Working Draft for a
transition WD>CR, or Candidate Recommendation for a transition
CR>PR))specLink
(a link to the latest published version of
your specification)wg
(the name of the working group)bugs2html assumes the following usage of Bugzilla:
FIXED
: The Working Group
has accepted the comment and the reviewer is satisfied.WONTFIX
: The Working Group
has not accepted the comment and the reviewer is satisfied.In addition to these two categories, there are four categories which don't rely on the Bugzilla "resolution" field:
externalComments
: the comment was made by somebody who is
not a participant of the working group.resolutionsWithoutResponse
: there is no resonse from the
reviewer to the resolution of the working group.reviewerNotSatisfied
: the reviewer is not satisfied.nonEditorialChange
: the change made in response to the
issue is non-editorial (i.e. a possibly substantive change).There are two ways to use these four categories:
externalComment
,
noResponse
, reviewerNotSatisfied
or
nonEditorialChange
.externalComment
, resolutionsWithoutResponse
,
reviewerNotSatisfied
or nonEditorialChange
) a
comma-separated list of the bug IDs relevant to the category.The latter method is faster than changing the bugzilla entries themselves.
... you have probably used other fields than "resolution" in Bugzilla to
express the relevant categories. In that case, you can adapt the XPath
expressions used by bugs2html to fulfill your needs: they are encapsulated in
the entities (see bugs2html-specinfo.dtd) wgAcceptsCommentXPath
,
wgRejectsCommentXPath
, reviewerSatisfiedXPath
,
reviewerNotSatisfiedXPath
, noResponseXPath
,
nonEditorialChangeXPath
and
externalCommentsXPath
.