You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 21, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Jun 21, 2023. It is now read-only.
Welcome to our first Development Sprint Issue tracking our release for October 1st!
Overview
Release Date: October 1st, 2018 Description: This development sprint will be focused on cloning, annotations, internationalization, and improvements to our metrics and documentation. Review Period: September 17th - 21st Expect to have all PRs for this release reviewed and merged by the end of the review period Testing Period: September 24th - 28th Expect to have the Master branch tested and the release prepped by the end of the testing period
Goals
Community Engagement Goal
Are there PRs from community members?
Hypothesis Pre-Release
We will be seeking to validate/invalidate to these hypothesis prior to release.
Hypothesis
Test
Status
Next Steps
Owner
Hypothesis Post-Release
We will be seeking to validate/invalidate to these hypothesis during the next development cycle.
One thing I've been thinking about in terms of this release tracker is that it's the high-level features in each release that will each have: hypotheses, metrics, tests, and documentation rather than all of those being separate things on their own.
Feature: Refactored Clone Dialog Owner: Steven Status: 💚 (On-track) Hypothesis: Repository lists will load faster increasing the number of clones from an org because folks are likely to continue to use our interface rather than another application. Clones from a URL will increase through our interface.
Feature: Internationalization and CrowdIn Support Owner:@grokys with an assist from @StanleyGoldman@jcansdale@maikebing Status: 💚 (On-track) Hypothesis: We have a lot of users who use Visual Studio in another language and we could increase the usage of extension by those users by translating, we could increase the number of users by having translations, and we could increase the number of community supporters (either through CrowdIn translations or through actual contributions). We would like to increase the support we give for community members contributing to our project - if we are accepting more PRs (e.g. this one) we could increase the contributions.
Feature: Check Run annotations Owner: Stanley Status: 🏈 (punted for next release while we continue to iterate) Hypothesis: Users will get more information about their build status inside of Visual Studio for each PR meaning they spend more time using our extension.
Activity
meaghanlewis commentedon Sep 20, 2018
One thing I've been thinking about in terms of this release tracker is that it's the high-level features in each release that will each have: hypotheses, metrics, tests, and documentation rather than all of those being separate things on their own.
Example:
Release milestone: https://github.com/github/VisualStudio/milestone/19
FEATURES / ENHANCEMENTS
Feature: Refactored Clone Dialog
Owner: Steven
Status: 💚 (On-track)
Hypothesis: Repository lists will load faster increasing the number of clones from an org because folks are likely to continue to use our interface rather than another application. Clones from a URL will increase through our interface.
NumberOfCloneViewGitHubTabNumberOfCloneViewEnterpriseTabNumberOfCloneViewUrlTabNumberOfGitHubClonesNumberOfEnterpriseClonesRelated PRs:
Feature: Internationalization and CrowdIn Support
Owner: @grokys with an assist from @StanleyGoldman @jcansdale @maikebing
Status: 💚 (On-track)
Hypothesis: We have a lot of users who use Visual Studio in another language and we could increase the usage of extension by those users by translating, we could increase the number of users by having translations, and we could increase the number of community supporters (either through CrowdIn translations or through actual contributions). We would like to increase the support we give for community members contributing to our project - if we are accepting more PRs (e.g. this one) we could increase the contributions.
Related PRs:
Feature: Check Run annotations
Owner: Stanley
Status: 🏈 (punted for next release while we continue to iterate)
Hypothesis: Users will get more information about their build status inside of Visual Studio for each PR meaning they spend more time using our extension.
BUGS
Bugs Resolved
PRs to Merge
Unified Clone - #1919
drguthals commentedon Sep 20, 2018
I LOVE this @meaghanlewis Thank you!