-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Add WinForms Team Workflow documentation #15026
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
LeafShi1
wants to merge
2
commits into
dotnet:main
Choose a base branch
from
LeafShi1:Create_winforms_workflow
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+125
−0
Open
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,126 @@ | ||
| # WinForms Team Workflow | ||
|
|
||
| This workflow applies to work items in the WinForms Runtime and Designer repositories. | ||
|
|
||
| ## Workflow Overview | ||
|
|
||
| Todo → Ready → In Progress → Validation → In Review → Done | ||
|
|
||
| --- | ||
|
|
||
| ## Todo | ||
|
|
||
| ### Description | ||
|
|
||
| The work item has been created but is not yet assigned for active work. | ||
|
|
||
| ### Entry Criteria | ||
|
|
||
| - A new issue, task, bug, or feature is added to the project. | ||
| - The work item requires triage or prioritization. | ||
|
|
||
| ### Exit Criteria | ||
|
|
||
| - An owner is assigned. | ||
| - The work item has enough information to begin planning or implementation. | ||
|
|
||
| --- | ||
|
|
||
| ## Ready | ||
|
|
||
| ### Description | ||
|
|
||
| The work item is assigned and ready to be started. | ||
|
|
||
| ### Entry Criteria | ||
|
|
||
| - An owner has been assigned. | ||
| - The scope and requirements are sufficiently clear. | ||
|
|
||
| ### Exit Criteria | ||
|
|
||
| - The assignee begins investigation, design, implementation, or documentation work. | ||
|
|
||
| --- | ||
|
|
||
| ## In Progress | ||
|
|
||
| ### Description | ||
|
|
||
| The assignee is actively investigating, designing, implementing, or documenting the work item. | ||
|
|
||
| ### Entry Criteria | ||
|
|
||
| - Active work has started. | ||
|
|
||
| ### Exit Criteria | ||
|
|
||
| - The implementation or other planned work is functionally complete. | ||
| - A pull request is available for applicable validation activities. | ||
|
|
||
| --- | ||
|
|
||
| ## Validation | ||
|
|
||
| ### Description | ||
|
|
||
| The change is undergoing quality verification before FTE review. | ||
|
|
||
| Required validation activities include: | ||
|
|
||
| - Self-review by the assignee | ||
| - Internal peer review | ||
| - Appropriate Functional Validation | ||
| - Appropriate Regression Testing | ||
|
|
||
| Depending on the scope and risk of the change, additional verification activities may be required, such as Test Team validation. | ||
|
|
||
| ### Entry Criteria | ||
|
|
||
| - The implementation is functionally complete. | ||
| - The pull request is available for validation activities. | ||
|
|
||
| ### Exit Criteria | ||
|
|
||
| - All validation activities have been completed. | ||
| - Validation findings have been addressed. | ||
| - The pull request is ready for FTE review. | ||
| --- | ||
|
|
||
| ## In Review | ||
|
|
||
| ### Description | ||
|
|
||
| The pull request has completed the applicable pre-FTE validation and is waiting for FTE review and approval. | ||
|
|
||
| ### Entry Criteria | ||
|
|
||
| - The pull request is ready for FTE review. | ||
| - The "Waiting Review" label is applied when applicable. | ||
|
|
||
| ### Exit Criteria | ||
|
|
||
| - Required review feedback has been addressed. | ||
| - Required approval has been received. | ||
| - The pull request is ready to merge. | ||
|
|
||
| --- | ||
|
|
||
| ## Done | ||
|
|
||
| ### Description | ||
|
|
||
| The planned work has been completed and accepted. | ||
|
|
||
| Any planned post-merge Test Team validation may continue as a separate validation activity and may result in follow-up work if issues are found. | ||
|
|
||
| ### Entry Criteria | ||
|
|
||
| - The pull request has been merged. | ||
| - Or the work item has otherwise met its agreed completion condition. | ||
|
|
||
| ### Exit Criteria | ||
|
|
||
| - None. | ||
|
|
||
| This is the final workflow state. | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.