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

Prepare for Plone 6.1 release #1845

Merged
merged 5 commits into from
Feb 8, 2025
Merged

Prepare for Plone 6.1 release #1845

merged 5 commits into from
Feb 8, 2025

Conversation

stevepiercy
Copy link
Contributor

@stevepiercy stevepiercy commented Feb 7, 2025

TODO:

  • After the release, we need to run pipx run cookieplone project --no-input and replace the current console output with the command's in docs/install/create-project-cookieplone.md.

Refs plone/Products.CMFPlone#4101


📚 Documentation preview 📚: https://plone6--1845.org.readthedocs.build/

TODO:

- [ ] After the release, we need to run `pipx run cookieplone project --no-input` and replace the current console output with the command's in `docs/install/create-project-cookieplone.md`.
mauritsvanrees
mauritsvanrees previously approved these changes Feb 7, 2025
Copy link
Member

@mauritsvanrees mauritsvanrees left a comment

Choose a reason for hiding this comment

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

LGTM, thanks.

I did not think we would remove lines that say which Python version to use for Plone 6.0. But since 6.0 is strictly speaking already out of maintenance support, or will be once 6.1 final is out, I guess this cleanup makes sense. Otherwise there is just too much information, and people will get confused.

@stevepiercy
Copy link
Contributor Author

@mauritsvanrees yup, this was one of the trade-offs between completeness and simplification. In this case, less detail is more helpful, especially in how-to guides.

Copy link
Contributor Author

@stevepiercy stevepiercy left a comment

Choose a reason for hiding this comment

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

@mauritsvanrees @davisagli which is preferred here, 6.1-latest or 6.1.0? I think 6.1-latest is preferred so that we don't have to update the commands for patch releases.

@davisagli
Copy link
Member

@stevepiercy Yes, I would go with 6.1-latest

@stevepiercy
Copy link
Contributor Author

We can ignore the failed linkcheck for docutils, as sourceforge is temperamental. Let's wait for the RTD check.

@stevepiercy stevepiercy merged commit d633bbb into 6.0 Feb 8, 2025
3 checks passed
@stevepiercy stevepiercy deleted the 6.1-release branch February 8, 2025 00:03
Copy link
Member

@mauritsvanrees mauritsvanrees left a comment

Choose a reason for hiding this comment

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

This seems fine now. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants