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

Fixes handbook links (#8195)

Browse Source 
The links without https:// do not work.
This commit is contained in:
Luke Heath 2022-10-12 16:25:01 -05:00 committed by GitHub
parent fae8e4ca2c
commit 7e642eee96
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/Contributing/Releasing-Fleet.md
View File

@ -11,7 +11,7 @@ The current release cadence is once every three weeks and concentrates around We
To make sure we build quality releases, Fleet has a freeze period for testing prior to each release. To make sure we build quality releases, Fleet has a freeze period for testing prior to each release.
Effective at the start of the freeze period, we will not merge new feature work. Effective at the start of the freeze period, we will not merge new feature work.
When bugs are found during release testing, use the process documented in [our handbook](fleetdm.com/handbook/quality#release-testing). When bugs are found during release testing, use the process documented in [our handbook](https://fleetdm.com/handbook/quality#release-testing).
Release bugs are exempt from the freeze period. Release bugs are exempt from the freeze period.
### What to do? ### What to do?
@ -100,7 +100,7 @@ Note: Please prefix versions with `fleet-v` (e.g., `fleet-v4.0.0`) in git tags,
### Patch releases ### Patch releases
A patch release is required when a critical bug is found. Critical bugs are defined in [our handbook](fleetdm.com/handbook/quality#critical-bugs). A patch release is required when a critical bug is found. Critical bugs are defined in [our handbook](https://fleetdm.com/handbook/quality#critical-bugs).
#### Process #### Process