1

Milestone Lifecycle

Victor Nakoryakov edited this page 2018-06-14 14:36:04 +03:00

Table of Contents

• Planning
• Running
• Finishing
• Retrospective

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

A milestone in XOD (aka Sprint) is a series of development activities which result in releasing a new minor/major version of IDE.

Planning

• Each developer adds an issue with the t:refactor label onto the top of the sprint backlog. This action expels the technical debt on a regular basis. The refactoring may be started right away, while the core issues are being prepared.
• The goal of the sprint is set from the user’s point of view.
• A new GitHub milestone is created with the goal in its description.
• An announcement TOC is prepared.
• The annnouncement pulls GitHub issues related to stdlib improvements. They are created and added to the milestone.
• The stdlib issues pull IDE and core features. They are issued and added to the milestone.
• The issues are estimated in story points.
• Feature creep is detected and thrown out or extracted to separate issues out of the milestone.

Running

• Take an issue from the top of the “Sprint To Do” backlog
• Develop, PR, merge
• Repeat

Finishing

• Build a pre-release
• Write, PR, and merge a changelog update
• At the morning of the next day make a public release

Retrospective

• Everyone answers two questions about the system:
  1. What should we start doing in the Milestone Lifecycle?
  2. What should we stop doing in the Milestone Lifecycle?
• The changes are reflected in this document