Remove changes files. Update release process. Update support process (#1492)

- Remove changes files that were collected during the 4.1.0 release cycle
- Add removing changes files step to release process documentation
- Update support process docs to reflect the change to discussing the last on-call rotation at 🍽️  Daily standup meeting
This commit is contained in:
noahtalerman
2021-07-27 17:06:16 -04:00
committed by GitHub
parent 6c36a0babc
commit da7925e1d7
35 changed files with 2 additions and 53 deletions
-1
View File
@@ -1 +0,0 @@
* Make sure to fetch all host data when listing hosts. Fixes issue 1208.
-1
View File
@@ -1 +0,0 @@
* Return distinct error messages when Authorization header is missing vs when the token is wrong. Fixes issue 1239.
-8
View File
@@ -1,8 +0,0 @@
- Add `USERS_ADMIN` endpoint to `fleet/endpoints`
- Add `createUserWithoutInvitation` action to `redux/nodes/entities/users`
- Revise `UserManagementPage`
- Revise `UserForm`
- Update existing Cypress test
- Remove `renderSmtpWarning` from `UserManagementPage`
Implements #369
-1
View File
@@ -1 +0,0 @@
* Fix compatibility with GCP Memorystore Redis due to missing CLUSTER command.
-1
View File
@@ -1 +0,0 @@
* Fix printing of failed record count in AWS Kinesis/Firehose logging plugins.
-4
View File
@@ -1,4 +0,0 @@
- Update create/edit user modal to accurately reflect if SSO is enabled for the individual user (rather than if enabled for the organization as a whole)
- Update create/edit user modal tooltips and disabled fields based on state of organization settings (SSO and SMTP)
Closes #1348
-1
View File
@@ -1 +0,0 @@
Enhance DataTable and related components to enable multiple buttons for actions on selected rows
-1
View File
@@ -1 +0,0 @@
Add new activity feed to homepage
@@ -1,2 +0,0 @@
* Reduce the amount of inserts and deletes are done in the database when updating each host's
software inventory. Fixes issue 1009
-3
View File
@@ -1,3 +0,0 @@
* Packs success and error messages render
* Updates styling of flash messages
* Success flash message only persists for 4 seconds
@@ -1 +0,0 @@
* Empty state when trying to assign user to teams if no teams exist
-1
View File
@@ -1 +0,0 @@
* When creating packs, store the host, label, and team ids provided. Fixes issue 1206
-1
View File
@@ -1 +0,0 @@
* Adds APIs for working with the Global Schedule. Fixes issue 1231
@@ -1,2 +0,0 @@
* Actions dropdown matches wireframes
* Fix spacing, arrow, coloring
-1
View File
@@ -1 +0,0 @@
* Add mechanism so that only one instance of the horizontally deployed fleet servers runs the cleanups and other jobs alike. Fixes issue 1278
-1
View File
@@ -1 +0,0 @@
* Improve error messages at the API level. Fixes issue 1286.
-1
View File
@@ -1 +0,0 @@
* Make sure that all the global roles are within the expected values. Fixes issue 1292.
-1
View File
@@ -1 +0,0 @@
* Adds host users list and API. Fixes issue 1300
@@ -1,2 +0,0 @@
* Adds homepage to Fleet app
* Host Summary is displayed on Homepage
-1
View File
@@ -1 +0,0 @@
* If enabled, it sends usage analytics to fleetdm.com. Fixes issue 1321
-1
View File
@@ -1 +0,0 @@
* Add activities API that shows changes across the platform as users take action. Resolves issue 1324
@@ -1 +0,0 @@
* Fix an issue with data migrations where enroll secrets will end up duplicated after the name column removal. Fixes issue 1329
@@ -1 +0,0 @@
* New Schedule page feature allows users to create and remove queries from a global schedule applying to all hosts
@@ -1,2 +0,0 @@
* Dropdown CSS compatible with firefox
* Correct row heights rendering in Firefox tables
@@ -1 +0,0 @@
* Add host transfer capabilities to fleetctl. Fixes issue 1359.
-1
View File
@@ -1 +0,0 @@
* Add user delete capabilities to fleetctl. Fixes issue 1360
@@ -1,3 +0,0 @@
* Refactore software inventory table on host details page to use TableContainer
* Now searchable, shows count, reorder by name and type
* Vulnerabilities flag still sleeper feature in frontend waiting for backend work
@@ -1 +0,0 @@
* Change fleetctl get hosts to respond with host "status", "display_text", and "labels". Fixes issue 1373
-1
View File
@@ -1 +0,0 @@
* Clean placement, size, and position of tooltip/hover area
@@ -1 +0,0 @@
* Reorder hosts and user UI tables in ascending order (A-Z)
-1
View File
@@ -1 +0,0 @@
* When disabling SSO at the org level, disable it for all users. Fixes issue 296
@@ -1 +0,0 @@
* Fix bug where it was not possible to clear host settings by applying config. Fixes issue 872.
-1
View File
@@ -1 +0,0 @@
* Remove YUM and APT sources from software inventory. Fixes issue 966.
+1 -1
View File
@@ -2,7 +2,7 @@
Note: Please prefix versions with `v` (eg. `v4.0.0`) in git tags, Helm charts, and NPM configs.
1. Update the [CHANGELOG](../../CHANGELOG.md) with the changes that have been made since the last Fleet release. Update the NPM [package.json](../../tools/fleetctl-npm/package.json) with the new version number (do not yet `npm publish`). Update the [Helm chart](../../charts/fleet/Chart.yaml) and [values file](../../charts/fleet/values.yaml) with the new version number.
1. Update the [CHANGELOG](../../CHANGELOG.md) with the changes that have been made since the last Fleet release. Update the NPM [package.json](../../tools/fleetctl-npm/package.json) with the new version number (do not yet `npm publish`). Update the [Helm chart](../../charts/fleet/Chart.yaml) and [values file](../../charts/fleet/values.yaml) with the new version number. Remove all files from the `/changes` top-level directory except for the `.keep` file.
Commit these changes via Pull Request and pull the changes on the `main` branch locally. Check that `HEAD` of the `main` branch points to the commit with these changes.
+1 -1
View File
@@ -6,7 +6,7 @@ The support process is accomplished via an on-call rotation and the weekly on-ca
The individual on-call is responsible for responding to Slack comments, Slack threads, and GitHub issues raised by customers and the community.
The on-call retro meeting at Fleet provides time to discuss highlights and answer the following questions about the previous week's on-call:
The daily standup meeting at Fleet provides time to discuss highlights and answer the following questions about the previous week's on-call:
1. What went well?