Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have a question related to the release notes.

We have made several changes to the Primary Metric editor across multiple PRs:

The most recent PRs modify things that were already changed in previous PRs.

In cases like this, is it ok to provide a single release note that summarizes the final state?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, we can do that in two ways:

  • For 9.3 or earlier: Manually by editing the release notes PR, such as this one that will be reviewable later this week after we do a first pass of cleanup: [Docs] Kibana release notes for 9.3.0 #248511
  • For the future: you can mark PRs as release_note:skip and write up a small ## Release Note section in the most significant one that describes the final state.

Original file line number Diff line number Diff line change
Expand Up @@ -768,8 +768,8 @@ function StaticColorControl({
setColor: (color: string) => void;
swatches?: string[];
}) {
const colorLabel = i18n.translate('xpack.lens.metric.selectColor.label', {
defaultMessage: 'Select color',
const colorLabel = i18n.translate('xpack.lens.metric.colorLabel', {
defaultMessage: 'Color',
});

const { inputValue: currentColor, handleInputChange: handleColorChange } =
Expand Down