We are back from the holidays and are rolling again. We are starting to target our next important milestone for Code, the Build 2016 conference, which takes place at end of March in San Francisco. The roadmap outlines our high level plans for getting there and this is our detailed plan for the January 2016 iteration.
We plan to declare General Availability ("GA") with the March 2016 release. GA comes with several quality obligations in areas such as accessibility and localization. We know that we have significant gaps here and we want to start to tackle them right away. On the drive to Connect(); we accumulated engineering debt that we must to address sooner rather than later. And, as we always do, we will continue to ship monthly and address key development pain points and adoption blockers.
Based on these imperatives we arrived at the following themes for January:
- Ramp up the work to get to GA (accessibility, localization, ...).
- Reduce the engineering debt.
- Respond to feedback and try to address as many issues as possible.
The January Test Plan is in progress.
Schedule
The goal is to make the January update available by the following dates.
End game dates (we end an iteration with an endgame)
- Monday Jan 25th evening (GMT+1): freeze
- Tuesday: test day
- Wednesday: fix day
- Thursday: fix day
- Friday: Done: documentation, release notes update, bugs verified
⚠️ update we will switch to dev channels and deprecate the insider channel. We will make the new dev channels available as soon as possible during the end game and will hold back updating the stable channel until we have received early feedback.
Plan Items
🏃 = work in progress
✋ = task is blocked
💪 = stretch goal for this iteration
Feedback
Issues to address feedback from the community:
Debt Items
This section lists items to reduce our engineering debt:
Adoptions
We continuously have to adopt components which we require:
Engineering Items
This section lists several engineering/development items that the team identified:
Initial Investigations
Bugs
This section includes bug queries for the vscode related repositories:
For more information about our development process please refer to the development process page.
We are back from the holidays and are rolling again. We are starting to target our next important milestone for Code, the Build 2016 conference, which takes place at end of March in San Francisco. The roadmap outlines our high level plans for getting there and this is our detailed plan for the January 2016 iteration.
We plan to declare General Availability ("GA") with the March 2016 release. GA comes with several quality obligations in areas such as accessibility and localization. We know that we have significant gaps here and we want to start to tackle them right away. On the drive to Connect(); we accumulated engineering debt that we must to address sooner rather than later. And, as we always do, we will continue to ship monthly and address key development pain points and adoption blockers.
Based on these imperatives we arrived at the following themes for January:
The January Test Plan is in progress.
Schedule
The goal is to make the January update available by the following dates.
End game dates (we end an iteration with an endgame)
dev channelsand deprecate theinsider channel. We will make the new dev channels available as soon as possible during the end game and will hold back updating the stable channel until we have received early feedback.Plan Items
🏃 = work in progress
✋ = task is blocked
💪 = stretch goal for this iteration
Feedback
Issues to address feedback from the community:
DarkandLitethemes @aeschliDebt Items
This section lists items to reduce our engineering debt:
project.jsonis currently hard coded into JSON language, Enable that this can be contributed by the C# extension.Adoptions
We continuously have to adopt components which we require:
Engineering Items
This section lists several engineering/development items that the team identified:
Initial Investigations
Bugs
This section includes bug queries for the vscode related repositories:
For more information about our development process please refer to the development process page.