Use of Project in GitHub repo to track spec versions

[Jeff Mesnil]

Hi,

We just had the Health call today and, based on the conversation I wanted to update some issues to postpone them for Health 1.1, etc.

I can't create labels so I only added some comments but it made me wonder if we should instead use Projects[1] to track progress of the spec in a more "Kanban" style.

We could have a Project for Healthcheck 1.0 and one for Healthcheck 1.1 (and later).

Or should we stick to labels (like config does) such as healthcheck-1.0, healthcheck-later, etc.?

Has someone any experience with GitHub projects?

[1] https://help.github.com/articles/about-project-boards/

[John D. Ament]

I've tried it before, in other projects.  I find milestones easier to deal with, they more closely relate to releases in other bug tracking tools.  If you want I can setup some milestones for you.

John

[Ondro Mihályi]

I've never tried the "Projects" feature of github, I didn't even know about it. If John says it's more cumbersome than labels and milestones, I believe him, but you may wnat to try the "Projects" feature as well and judge for yourself.

Since you're not the Eclipse project committer, you don't have permissions to create labels and milestones. 

In that case, I suggest creating an issue in the github repository in which you'd like to create labels and milestones and specify what you'd like to have. Anybody from the project committers can do that for you and I believe that at least some of them would get a notification about your issue and will react. I say that because I usually turn off notifications for repositories I'm not actually interested in to avoid flooding my mailbox. If nobody reacts, the next step would be to ask on the mailing list and point to the issue you need to get solved.

--Ondro