Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

whats new page #314

Closed
oliver-sanders opened this issue Nov 8, 2021 · 5 comments · Fixed by #510
Closed

whats new page #314

oliver-sanders opened this issue Nov 8, 2021 · 5 comments · Fixed by #510
Labels
content Addition or modification of documentation
Milestone

Comments

@oliver-sanders
Copy link
Member

oliver-sanders commented Nov 8, 2021

We should include the changelog(s) in the docs, note Sphinx can handle markdown if needed.

We could do with a list of major changes for each Cylc meta-package release, could do that in the changelog files or, alternatively collate the major changes from the different repos into a page here.

Note: We can document changelog files (Sphinx does support Markdown). It would be nice to document these (changelogs will then appear in search results).

Note: We currently have a "major changes" page detailing Cylc < 8 versions.

Question:

  • Are we happy to compile the major changes for a release here or is there a better place?
  • Should we document maintenance releases or just minor releases?
@oliver-sanders oliver-sanders added content Addition or modification of documentation question Further information is requested labels Nov 8, 2021
@oliver-sanders oliver-sanders added this to the 8.x milestone Feb 7, 2022
@oliver-sanders
Copy link
Member Author

Suggest creating a "what's new" or "changes" page with a hand-crafted summary of major changes across the projects similar to the Python highlights page.

Then incorporating the changelog files from the individual projects.

@hjoliver
Copy link
Member

hjoliver commented Aug 10, 2022

Yes, I like that approach.

If no one objects, we can remove the question label at the meeting, and move on with this.

@wxtim
Copy link
Member

wxtim commented Aug 10, 2022

I agree with this approach - I think that we need to keep editorial control of the top level headlines, but if it's simple enough we can also include all changelogs as well.

@hjoliver
Copy link
Member

(whole project/ multi-repo)

@oliver-sanders oliver-sanders removed the question Further information is requested label Aug 11, 2022
@oliver-sanders
Copy link
Member Author

oliver-sanders commented Aug 11, 2022

Discussed at developers meeting.
[HO] we agreed with this approach. Manual cross-component write-up required, but should be quick.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Addition or modification of documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants