Rules for managing issues on GitHub

[Thomas Broyer]

Hi all,

Here's a document a wrote (months ago actually) about the differences between Google Code Hosting and GitHub wrt their respective issue trackers.

https://docs.google.com/document/d/1yJva4UWQ7XO-gGtFm4ykXt0tubn9j1nncWPPz57IH9M/edit

We discussed it briefly at our last Steering Committee meeting last Wednesday and, as no one had objections, we decided that we'd share it here and seek feedback for a week before setting (some of) those rules in stone.

I propose short-term goals of:

• deleting old labels (e.g. ReviewBy-* labels)
• using the Review-Pending label and adding links to the reviews in comments
• using milestones and closing issues when resolved (rather than using a FixedNotReleased label)

We can sort out other details (assignment, etc.) later, but your feedback is welcome.

I'd also like to align Category-* labels with the "modules" from https://docs.google.com/document/d/1vyncxfuujIJ3L-PBLNM68tfeXRFZ4qDdnWEodblmvRg/edit

Thanks in advance.

[Stanislav Spiridonov]

Hi, 

our last Steering Committee meeting last Wednesday

Please, publish meeting notes, if it is't a secrete :) 

Best,

Stas

[Thomas Broyer]

On Friday, March 18, 2016 at 10:52:14 AM UTC+1, Stanislav Spiridonov wrote:

Hi, 

our last Steering Committee meeting last Wednesday

Please, publish meeting notes, if it is't a secrete :)

Daniel (cc'd) was taking the notes during the meeting; let's ask him ;-)

[Jens]

Ok I have added a bunch of feedback comments directly in the document.

In general I think its fine although we should try hard to minimize labels and use good colorization of labels.

-- J.

[Thomas Broyer]

FWIW, I started doing some of the things I highlighted in the document:

• created GitHub milestones and replaced the Milestone-* labels with assignments to the corresponding milestone, for all releases back to 2.1.0 (older release still to be migrated). When there was labels for RCs, I merged them all into the final release; that was only affecting old releases for which we don't need to keep such level of details.
• assigned all FixedNotReleased issues to the 2.8 milestone, closed them, and deleted the label.
• deleted all ReviewBy-* labels.

On Monday, March 14, 2016 at 1:19:23 AM UTC+1, Thomas Broyer wrote:

[Daniel Kurka]

Nice work Thomas, really appreciated!

--
You received this message because you are subscribed to the Google Groups "GWT Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-co...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/010b67c4-84e9-413d-ad60-9989741adbb4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Thomas Broyer]

Hope I didn't spam you too much ;-)

On Thursday, April 14, 2016 at 4:13:09 PM UTC+2, Daniel Kurka wrote:

Nice work Thomas, really appreciated!

On Thu, Apr 14, 2016 at 4:11 PM Thomas Broyer <t.br...@gmail.com> wrote:

FWIW, I started doing some of the things I highlighted in the document:

• created GitHub milestones and replaced the Milestone-* labels with assignments to the corresponding milestone, for all releases back to 2.1.0 (older release still to be migrated). When there was labels for RCs, I merged them all into the final release; that was only affecting old releases for which we don't need to keep such level of details.
• assigned all FixedNotReleased issues to the 2.8 milestone, closed them, and deleted the label.
• deleted all ReviewBy-* labels.

On Monday, March 14, 2016 at 1:19:23 AM UTC+1, Thomas Broyer wrote:

Hi all,

Here's a document a wrote (months ago actually) about the differences between Google Code Hosting and GitHub wrt their respective issue trackers.

https://docs.google.com/document/d/1yJva4UWQ7XO-gGtFm4ykXt0tubn9j1nncWPPz57IH9M/edit

We discussed it briefly at our last Steering Committee meeting last Wednesday and, as no one had objections, we decided that we'd share it here and seek feedback for a week before setting (some of) those rules in stone.

I propose short-term goals of:

• deleting old labels (e.g. ReviewBy-* labels)
• using the Review-Pending label and adding links to the reviews in comments
• using milestones and closing issues when resolved (rather than using a FixedNotReleased label)

We can sort out other details (assignment, etc.) later, but your feedback is welcome.

I'd also like to align Category-* labels with the "modules" from https://docs.google.com/document/d/1vyncxfuujIJ3L-PBLNM68tfeXRFZ4qDdnWEodblmvRg/edit

Thanks in advance.

--
You received this message because you are subscribed to the Google Groups "GWT Contributors" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscribe@googlegroups.com.