Interview with Aaron Bjork (Release Notes)

01/09/18 • 17 min

In this interview, Principal DevOps Manager Donovan Brown interviews Principal Group Program Manager Aaron Bjork about how the release notes for VSTS are generated for each release.

[00:50] Set the stage
[01:15] Release Notes Page
[02:14] How are they created
[02:40] DoD
[03:12] Not everything requires release notes
[03:53] Feature Flags!
[04:40] Release notes in action
[05:04] Delivery Plans
[06:19] When do we set the flag?
[06:52] When should you write the release notes?
[08:45] How do you find all the release notes?
[09:35] Sprint mails
[11:20] The query of items needing release notes
[12:10] Bringing it all together with Markdown
[13:42] Pull requests
[15:45] Keys to making it work

Blog: DonovanBrown.com
Follow @DonovanBrown

Follow @aaronbjork

In this interview, Principal DevOps Manager Donovan Brown interviews Principal Group Program Manager Aaron Bjork about how the release notes for VSTS are generated for each release.

Blog: DonovanBrown.com
Follow @DonovanBrown

Follow @aaronbjork

Previous Episode

Interview with Munil Shah (Quality)

In this interview, Director of Engineering Munil Shah returns to share insights on how our quality practices had to change to support of Visual Studio Team Services.

[00:43] Quality in the Cloud cadence
[02:00] Types of tests
[03:59] New Approach
[05:37] Shift Left
[07:09] Combined Engineering
[13:30] Quality Vision
[21:27] Pull Request
[24:54] Advice for others
[28:39] Rolling CI Pipeline

Next Episode

How Windows, Windows Store, Xbox and Surface streamlined their planning process and centralized on VSTS

In this video Donovan Brown interviews Jill Campbell, Group Program Manager who works in the Windows and Devices Group (WDG), Engineering Systems team, overseeing the process and tools Windows uses to plan work across tens of thousands of employees and an extensive portfolio of products including Xbox, Surface, Windows Store and of course the Windows operating system itself.

Throughout the interview Jill will describe how Windows moved all these product teams from various tools to a unified process powered by Visual Studio Team Services (VSTS), and how VSTS scales for them along with the flexibility and customizability which enabled them to be successful in managing over 11 million work items, across 33,000 users (across all of Microsoft) and with teams varying in processes ranging from Agile through to Waterfall.