elastic
docs: qualifier
Motivation/summary
update docs after the recent changes from https://github.com/elastic/apm-server/pull/15350
Checklist
- [ ] Update CHANGELOG.asciidoc
- [ ] Documentation has been updated
For functional changes, consider:
- Is it observable through the addition of either logging or metrics?
- Is its use being published in telemetry to enable product improvement?
- Have system tests been added to avoid regression?
How to test these changes
Related issues
:robot: GitHub comments
Expand to view the GitHub comments
Just comment with:
-
rundocs-build: Re-trigger the docs validation. (use unformatted text in the comment!)
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
If this is only something to consider for MAJOR, maybe we should put it under the Major Release header?
If this is only something to consider for MAJOR, maybe we should put it under the Major Release header?
I don't know, the qualifier is release agnostic but we used it only for MAJOR releases.
In that case, I'd still prefer it under Major Release, since that is the only case when we should consider taking it into account. cc @carsonip for an extra take on this. We can always move it out, when we end up using it for non-majors.
That's still part of the Between feature freeze and release section, regardless of the type of release.