in src/pages/release-notes/wizard.tsx [233:272]
not been released (yet). For the release note generation to work, please mark
versions that will still be released. Leave versions unmarked if there is no
release planned for this version.
<EuiSpacer size="s" />
<EuiAccordion id="unreleasedVersionMoreDetails" buttonContent="More details">
<EuiSpacer size="s" />
<p>
<strong>How does this tool determine PRs for a version?</strong> Version
labels on PRs determine in which version's release note a PR appears. The
way version labels are used in the repository, can cause a PR to have
multiple version labels attached. That PR should nevertheless only show up
in the earliest version it got released, e.g. a PR with the labels v7.10.2,
v7.11.0 and v8.0.0 should only appear in the v7.10.2 release notes. This
tool makes sure it will only be included in the release note of the earliest
version.
</p>
<p>
<strong>What is the problem with unreleased version labels?</strong> PRs
with a version label assigned for a version that never will be released are
causing problems. Scenario: a PR has the labels v7.10.3, v7.11.1, v7.12.0,
v8.0.0 with 7.10.3 never being an actual release. This tool would now assume
that this PR should show up in v7.10.3's release notes, which never existed,
and thus the PR will never be listed in any release notes.
</p>
<p>
<strong>Why do those unreleased labels exist?</strong> Sometimes the release
was originally planned and then canceled, sometimes some engineer created
that label while that release was never planned and then the label ended up
on more and more PRs.
</p>
<p>
<strong>What do I need to do here?</strong> This tool retrieves a list of
existing version labels from the two minor versions prior to the selected
version. It will check if any of them does not match an existing release.
For each of those version labels without a matching release you'll need to
specify how it should be treated:
</p>
<div>
<EuiSwitch
checked={true}