-
Notifications
You must be signed in to change notification settings - Fork 225
Planning
The team has a 6-month high level Roadmap which defines high-level themes and features to be addressed in this timeframe.
The work planned during an iteration is captured in the iteration plan (see Iteration Plans). The feature highlights of each iteration are highlighted in the release notes.
Before each month, we prioritize features and changes to the service we plan to make in the next iteration. For features, change requests and bugs planned for an iteration, we will create new issues and label them with plan item and add a milestone for the specific month the iteration represents. Change requests, feature requests, and bugs that are assigned to a milestone encompass the planned work for the upcoming month.
Reported bugs are placed into the bug inbox until triaged and assigned to someone on the App Center team. We'll discuss details of the issue with you directly to see how we can resolve your issue.
We don't always create the best experience right away, but we are committed to getting there. Create a change request for us to discuss changes we should make to existing functionality.
We might not be able to do everything at once, but that. We'll open pull requests against these Github issues so you can share your feedback during the design discussion.
Bugs, change requests, features and proposals are plan items added to iteration plans every month. We'll openly discuss design details and share early designs of the features we are working on.
Our roadmap provides a general guide for where our core priorities stand. A significant portion of our team are focused on delivering roadmap items every iteration, but bugs and change requests will be selected to address issues impacting your everyday use of the service.
Each week we will manage work items, crossing off completed features, triaging issues and publishing updates on our progress. Some changes and enhancements will then be either postponed to later iteration or moved back to the backlog.
At the end of each iteration, we will publish a recap of our progress and what was successfully shipped.
Project Management
Resources