Documentation: always check-in vendor - Githubissues

fru-io / handbook

How we work at DDEV

https://handbook.ddev.com

Creative Commons Attribution 4.0 International

10 stars 13 forks source link

Documentation: always check-in vendor #58

Open dclear opened 4 years ago

dclear commented 4 years ago

Feature Description:

Add to developer process documentation that we want to always check-in vendor and keep it up to date.

User stories:

As an engineer at DDEV, I want to have process docs I can reference so I can stay consistent with company policies and best practices

Acceptance criteria:

Write up and PR to developer handbook policy instructions on checking in vendor directories when developing on the platform.

Related links or issues:

Definition of Ready Checklist:

[x] User-facing feature: provides story or A/C in Gherkin format, or
[ ] Architectural feature: provides technical A/C
[ ] Dependencies identified
[ ] Sized by team

R^{Product Owner} A^{Scrum Master} C^{Eng. Lead} I^Team

Definition of Done Checklist:

[ ] Acceptance Criteria tested and passing
[ ] Deployed on test environment
[ ] QA performed & issues resolved
[ ] Unit test and E2E coverage updated (if applicable)
[ ] Builds without errors
[ ] Internal documentation updated (if required)

R^{Eng. Lead, Team} A^{Scrum Master} CI^{Product Owner}