shanedell commented on issue #1186: URL: https://github.com/apache/daffodil-vscode/issues/1186#issuecomment-2767537238
Its not generated at all its manually created. This is done through the [apache/daffodil-site](https://github.com/apache/daffodil-site) repository. On every new release candidate version these things have to be done: - Create a new file under `site/_vscode` with the release version as the name, e.g. `1.4.1.md`. - After that file is created I copy the main headers from a previous file, something like below: ```readme --- release: rc1 (replace with current rc version or "final" if rc moved to final release) apache: true title: <version> date: <date-rc1-was-created-and-put-out-for-vote> summary: <summary> source-dist: - "apache-daffodil-vscode-<version>-src.zip" binary-dist: - "apache-daffodil-vscode-<version>.vsix" --- <small description> #### New Features & Fixes #### Closed Issues ``` - Look at the closed tickets for the milestone version and start adding bullet points the file. - Create a PR to the daffodil-site repository - After each RC and and when an RC is promoted to final release, the file needs to be updated to keep track of where the release process is. - Once that initial PR is merged that release page will not be shown unless the value `released:` is set to `final` which is done after promoting a RC to final release. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
