Skip to content

Globalization

Updated Dec 12, 2019
  

Project for tracking globalization efforts in Storage Explorer.

Column Description
Committed Issues that have been chosen for work in an upcoming release. When committed, a milestone should be assigned to the issue. These issues should be moved to Localizing when work on them begins.
Localizing Issues related to hard-coded strings that need to be localized.
Context Needed Issues related to localized strings that need additional context from the developers before translation can occur.
Under Review Issues for which a code review related to localization is out and awaiting approval. When the pull request is completed, the issue should be moved to Translating.
Translating Issues related to localized strings that are ready for translation. Once completed, the issue should be moved to Verifying. If additional context is needed for a proper translation, the issue should be moved to Context Needed.
Verifying Issues related to translated strings that need to be verified in the application. Once a fix has been verified in the application, the issue can be closed and moved to Done.
Done Issues that have been resolved and closed.

Storage Explorer

Updated Dec 12, 2019
  

Project for tracking general Storage Explorer work.

Column Description
Blocked Issues that require external help before moving forward.
Committed Issues that have been chosen for work in an upcoming release. When committed, a milestone should be assigned to the issue. These issues should be moved to In Progress when work on them begins.
In Progress Issues currently being worked on by the assignee or asignees. Move the issue to Under Review when initial work is complete and a code review has been sent out.
Under Review Issues for which a code review is out and awaiting approval. When the pull request is completed, the issue can be closed and moved to Done. If the issue needs additional validation, it should be moved to Verifying.
Verifying Issues for which additional validation is needed before the issue can be closed. These may include localization issues, issues fixed in a separate package or extension, etc. If the issue is not resolved and needs additional work, it should be moved to *In Progress. Once verified, the issue may be closed and moved to Done.
Done Issues that have been resolved and closed. When a release occurs, all (closed) issues in this column assigned to the corresponding Milestone should be archived.

Forward Looking & Engineering

Updated Oct 12, 2018

Board for tracking engineering improvement tasks.

You can’t perform that action at this time.