Luke Heath

> A while ago we agreed to follow this strategy: https://github.com/fleetdm/fleet/blob/main/docs/Contributing/fleetd-development-and-release-strategy.md Thanks, Lucas! @kswagler-rh As defined in the document Lucas shared, our commitment is for new versions of `fleetd` to...

I am reclassifying this as a P2 per our new [product group priority system](https://fleetdm.com/handbook/company/product-groups#high-priority-user-stories-and-bugs). I am assigning @sharon-fdm and @noahtalerman to decide how to move forward on this.

As much information we can get about their environment is helpful. It will help us better replicate their environment and make our migration tests more effective.

@Patagonia121 Thank you! @noahtalerman I think the next step is to run load tests on each version to determine which are performant. That's going to take some resources, so we...

+1

@dantecatalfamo Thanks for filing this! This seems like an easy customer service win (@Patagonia121 @nonpunctual) so I'm prioritizing for estimation and to be considered for the next sprint.

Thanks for filing this. I re-spec'd as a bug, because our documentation does not match our API response. I'd like to keep `~engineering-initiated` to tickets filed by engineering.

@eashaw On the website endpoint, we should do some validation on what we'll accept as a version and if the parameter's value is invalid, we should return a 400 Bad...

@sharon-fdm Should we consider validating the Fleet server version before sending usage analytics? That way, we're not skewing the data with fake usage analytics.

@sharon-fdm Could we do it as part of this bug ticket and avoid the new issue?