RE: Github issues update

David,
The role of "Postpond" was for Active issues that were deferred when a new Process Document was in preparation. It meant that that issue would become Active again after the publication of the draft being prepared. This is equivalent to "Deferred to the next edition".

Also, my Adobe ID will cease working on 28 April when I retire. Please update my e-mail address to:
<steve@zilles.org>

Steve Z

-----Original Message-----
From: David Singer [mailto:singer@mac.com] 
Sent: Sunday, April 23, 2017 8:30 PM
To: public-w3process <public-w3process@w3.org>
Subject: Github issues update

Hi

when I moved the issues from the W3C Issue Tracker to GitHub, I replicated their W3C state with a GitHub issue tag, but it struck me that that was not optimal. 

W3C Issues have various states, among which are:

Raised — newly entered, not yet accepted as an issue by the group Open — taken up by the working group Pending Review — believed addressed, waiting for confirmation/acceptance Closed — obvious Postponed — not under active consideration, deferred to a future version

So I created a couple of tags:  PendingReview (matches), and ‘Active’ (which replaces the prior ‘open’ state).

If we need ‘postponed’ we can create it.  Newly entered issues are untagged and hence ‘Raised’; and issues can be closed.  So, the matching is, from old state to GitHub

Raised — no tag
Open: Active
Pending Review: PendingReview

I hope this helps; we can fiddle as needed (though it would be good if there were normal practice across all W3C groups).

Comments welcome

Dave Singer

singer@mac.com

Received on Monday, 24 April 2017 06:18:35 UTC