Update user_agent.* wording to support multiple apps

[trisch-me]

Fixes #662

Changes

Merge requirement checklist

• CONTRIBUTING.md guidelines followed.
• CHANGELOG.md updated for non-trivial changes.
• schema-next.yaml updated with changes to existing conventions.

[trask]

such as microservices with multiple applications

I didn't really follow, what would be an example this? thx

[trisch-me]

hey @trask sorry that it's not clear, probably I need to rephrase it anyway in this case.

I refer to the comments like we should expand user-agent to support all possible products inside user-agent and My ideal solution would be we define use agent name version to be "the outer most" or "most important" name/version found in the string. For YourApp/1.0.0 grpc-java-okhttp/1.27.2 I think this means YourApp and 1.0.0. from previous PR

[trisch-me]

@trask @joaopgrassi I have rephrased it. Please check it out

[joaopgrassi]

Hi @trisch-me !

We changed how the CHANGELOG.md is managed. Please take a look at https://github.com/open-telemetry/semantic-conventions/blob/main/CONTRIBUTING.md#adding-a-changelog-entry to see what needs to be done. Sorry for the disruption.

[trisch-me]

hey @joaopgrassi I haven't updated the changelog because it's only a new wording without bigger changes. Please let me know if you think I need to create a new entry for this PR

[trisch-me]

@joaopgrassi The same problem as in your recent PR (with WIP label), I don't have changes for changelog for this trivial PR but the job is failing and I don't have access to the labels in my current role.

[arminru]

@joaopgrassi The same problem as in your recent PR (with WIP label), I don't have changes for changelog for this trivial PR but the job is failing and I don't have access to the labels in my current role.

@trisch-me You can prefix the PR title with [chore] for the same effect but a changelog entry for the refinement and added note would be fine too I think.

[trisch-me]

@arminru I will add changelog entry but I think we need to update our rules as well. There are editorial PRs etc, we could add labels automatically using github actions

[arminru]

@arminru I will add changelog entry but I think we need to update our rules as well. There are editorial PRs etc, we could add labels automatically using github actions

For editorial PRs, if either the PR title is prefixed with [chore] or the Skip Changelog label is added, the check will pass.

Since merging is always done by a person and not a workflow, that person can just add the label as the very last action right before merging the PR (or the PR author themselves adds the PR title prefix). Until merging it's not an issue if that one merge check fails except for the visual cue it carries.