New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adopt GitHub Projects for issue prioritization #1205

Closed
borekb opened this Issue May 9, 2017 · 2 comments

Comments

Projects
1 participant
@borekb
Member

borekb commented May 9, 2017

  • Create GitHub projects, assign issues into them
  • Describe the approach in CONTRIBUTING.md.

@borekb borekb self-assigned this May 9, 2017

borekb added a commit that referenced this issue May 9, 2017

[#1205] Added GitHub Projects to CONTRIBUTING.md > Our development pr…
…ocess. Done some minor updates to the section as well.

borekb added a commit that referenced this issue May 9, 2017

@borekb

This comment has been minimized.

Member

borekb commented May 9, 2017

Created 3 projects for now:

I went through all the issue in the 4.0 milestone and assigned them to one of the three projects.

@borekb borekb added this to the 4.0 milestone May 9, 2017

@borekb borekb closed this May 9, 2017

@borekb

This comment has been minimized.

Member

borekb commented May 9, 2017

To repeat the most important thing about the milestone / project change:

  • Each issue should be assigned to a milestone as previously, no change there. (Milestones are rough categorization.)
  • Inside a milestone, each issue should be assigned to one specific project, e.g., an alpha project.

This should be done for both issues and pull requests.

@borekb borekb added this to Done in 4.0-beta May 18, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment