empayre/fleet
14
0
Fork 0
mirror of https://github.com/empayre/fleet.git synced 2024-11-06 08:55:24 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Clarify sprint naming (#12445)

Browse Source
This commit is contained in:
Mo Zhu 2023-06-21 14:56:54 -07:00 committed by GitHub
parent 2649073d91
commit 464edd0b40
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
handbook/product/README.md
View File

@ -98,7 +98,7 @@ On the first day of each release, all estimated issues are moved into the releva
Sprints are managed in [Zenhub](https://fleetdm.com/handbook/company/why-this-way#why-make-work-visible). To plan capacity for a sprint, [create a "Sprint" issue](https://github.com/fleetdm/confidential/issues/new/choose), replace the fake constants with real numbers, and attach the appropriate labels for your product group.
### Sprint numbering
Sprint 1 began at the beginning of January 2023. Sprint 4 began in late March 2023. And so forth.
Sprints are numbered according to the release version. For example, for the sprint ending on June 30th, 2023, on which date we expect to release Fleet v4.34, the sprint is called the 4.34 sprint.
### Product design conventions