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

Document how we manage Milestones, fixes #36 #58

Merged
merged 1 commit into from
Jun 30, 2015
Merged

Document how we manage Milestones, fixes #36 #58

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
19 changes: 18 additions & 1 deletion RELEASING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,10 +16,27 @@ There can also be an extra postfix to the version number, added to describe the
* v1.2.3-devel
* v1.5.5-preview

### Code names
### Code names

Release code-names might be exist, but will be used for purely cosmetic purposes. The *Happy Panda* release would just be a name for the v1.5.0 release.

### Managment

For each Milestone, 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.

Generally, it makes sense for each Milestone to represent a logical and descriptive amount of work. For example, a Milestone
could be about documentation, bug fixes, implementing a big new feature, refactoring, etc.

There is no specific defined time limit for a Milestone, but when it's created and issues triaged into it, it should be
factored in. Milestones that take too much time to complete are a bad practice. Better to split up work in multiple Milestones,
sequentially reached, instead of one big-bad Milestone.

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

The ultimate role of the Release Manager is to successfully complete the Milestone, with the help of the development team.

## Tags

Tags will be used to track releases of the Nubis Project.
Expand Down