Skip to content

Conversation

@himorin
Copy link
Contributor

@himorin himorin commented Dec 21, 2025

as title.

Also,,, how about:

  1. on previousMaturity and PreviousPublishDate

it seems:

  • Previous Versions in document details header has been made optional
  • we don't include previousPublishDate metadata but just have previousMaturity
  • respec documentation on previousMaturity routine does not check generated link is correct (by means, pair of maturity and published date)
  • published spec will have history link in its document details header

how about to remove both previousMaturity (line 18) and previousPublishDate (line 25)? (which also may cause our mistake!)

  1. use // instead of /* */ for comment

block type commented out is confusing and we may edit line by line, as well as switch enable/disable line by line, in metadata lines, how about not to use /* */?

@himorin
Copy link
Contributor Author

himorin commented Dec 21, 2025

ah, also how about to remove imsc1/spec/manifest.txt file which is no longer used?

if all three are fine for both @nigelmegitt and @palemieux , I would update this PR.

Comment on lines 4113 to +4115



Copy link
Contributor

Choose a reason for hiding this comment

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

Strange white space appended to end of file.

@nigelmegitt
Copy link
Contributor

ah, also how about to remove imsc1/spec/manifest.txt file which is no longer used?

if all three are fine for both @nigelmegitt and @palemieux , I would update this PR.

Happy to remove unused files. Does this have any interaction with PR Preview not working? Or was it only used for echidna auto-publication?

@himorin
Copy link
Contributor Author

himorin commented Jan 8, 2026

ah, also how about to remove imsc1/spec/manifest.txt file which is no longer used?
if all three are fine for both @nigelmegitt and @palemieux , I would update this PR.

Happy to remove unused files. Does this have any interaction with PR Preview not working? Or was it only used for echidna auto-publication?

this was used for locally executed automation tool (not sure it was echidna or not, but some command line tool without integration with spec building tool like bikeshed or respec), and not used for spec-prod GH workflow.
I have no idea with pr-preview, but I saw some repository had issue that pr-preview does not update issue description with built one in Dec last year, without any idea whether these are related or not.

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.

4 participants