Skip to content

Conversation

@tshepang
Copy link
Member

No description provided.

@tshepang tshepang requested a review from PLeVasseur January 29, 2026 07:43
Copy link
Contributor

@PLeVasseur PLeVasseur left a comment

Choose a reason for hiding this comment

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

I'm not sure if I'm doing this right 😅

Tried to find if any might be missing.

- :p:`fls_YDVgFaTQwcL8`
- :p:`fls_zv73CR8rplIa`
- :p:`fls_tZJgZDWVChJV`

Copy link
Contributor

Choose a reason for hiding this comment

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

In the "New paragraphs" list for this item, I think we're missing a few IDs from PR #631's spec changes:

Suggested change
- :p:`fls_LnPDQW3bnNUw`
- :p:`fls_sw6HrsxsnG2y`
- :p:`fls_urIJ5JNHLhm6`

Copy link
Member Author

Choose a reason for hiding this comment

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

skipped those since they are glossary entries, but am not sure I should have... what say @kirtchev-adacore

Copy link
Member Author

Choose a reason for hiding this comment

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

how I done it in the past is I would define the term inline, not in glossary, and it's then that I would add it to changelog

Copy link
Contributor

Choose a reason for hiding this comment

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

I think we should treat new paragraphs in the glossary as "regular" new paragraphs, and document them in the changelog.

Copy link
Member Author

@tshepang tshepang Feb 9, 2026

Choose a reason for hiding this comment

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

as agreed in the FLS meet, I replicated the glossary entry inline so that we can put it in the changelog, since the glossary is informational

also

  • fls_sw6HrsxsnG2y already has an entry inline
  • fls_urIJ5JNHLhm6 is a glossary-only reference, pointing to the section where the glossary entry is introduced inline

f667314

- :p:`fls_drb114dtvlpt`
- :p:`fls_uxysntb3u03j`
- :p:`fls_vstdqifqipbh`

Copy link
Contributor

@PLeVasseur PLeVasseur Jan 30, 2026

Choose a reason for hiding this comment

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

In the "Changed paragraphs" list, two IDs from PR 631's diff look missing. One is a list-structure shift (fls_wh201rmh6u6d), the other switches :dt: to :t: (fls_y3oputy9e0sz).

Suggested change
- :p:`fls_wh201rmh6u6d`
- :p:`fls_y3oputy9e0sz`

Copy link
Member Author

Choose a reason for hiding this comment

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

skipped those because I see them not as semantic changes

@tshepang tshepang requested a review from PLeVasseur February 9, 2026 15:28
Copy link
Contributor

@PLeVasseur PLeVasseur left a comment

Choose a reason for hiding this comment

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

Thanks @tshepang!

@tshepang tshepang added this pull request to the merge queue Feb 9, 2026
Merged via the queue into main with commit fb8a467 Feb 9, 2026
3 checks passed
@tshepang tshepang deleted the tshepang/missing-changelog-entries branch February 9, 2026 19:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants