- Main unit of work is issue
- Projects are views for the clients representing status of the current known requirements/issues
- Issue should be closed by the client after validation
- dev team then moves the issues from column to column (in projects)
- Labels are used to identify the source of the issue ( requirements/issues vs feedback from demos/etc)
- requirements should always link back to the DINA-Web specification repositories when applicable
- dev issues should link to GitHub issues, not the other way around
- milestones could be used to define the "version" where the issue will be addressed
-
Notifications
You must be signed in to change notification settings - Fork 2
AAFC-BICoE/dina-planning
Folders and files
| Name | Name | Last commit message | Last commit date | |
|---|---|---|---|---|
Repository files navigation
About
AAFC-DINA planning repository
Resources
Stars
Watchers
Forks
Releases
No releases published
Packages 0
No packages published