Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Roadmap: How is it managed? #36

Closed
gozer opened this issue Jun 15, 2015 · 2 comments
Closed

Roadmap: How is it managed? #36

gozer opened this issue Jun 15, 2015 · 2 comments
Labels
decision question
Milestone
v0.9.0

Comments

@gozer
Copy link
Contributor

gozer commented Jun 15, 2015

No description provided.

@gozer gozer added the question label Jun 15, 2015
@gozer gozer added this to the v1.0 milestone Jun 15, 2015
@gozer gozer added the decision label Jun 18, 2015
@gozer
Copy link
Contributor Author

gozer commented Jun 18, 2015

For each Milestone/Release, one of the Tech Leads takes on the Release Manager Hat.

That Release Manager is responsible for triaging what makes it into that Release, with input from the rest of the team.

For that Release, the RM gains a veto, solely for purposed of tie-breaking project blocking/delaying issues.

@gozer
Copy link
Contributor Author

gozer commented Jun 24, 2015

🕐 1h

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
decision question
Projects
None yet
Milestone
v0.9.0
Development

No branches or pull requests
1 participant
@gozer