Conversation
DO NOT MERGE until Plone 6.2 final is released. @mauritsvanrees here ya go!
mauritsvanrees
left a comment
There was a problem hiding this comment.
LGTM, thanks.
I think the changes you made to docs/backend/upgrading/version-specific-migration/upgrade-to-62.md and docs/conf.py can already be merged.
I guess theoretically we should wait with those until the next release is out, whether that is beta 1 or RC 1, because the current alpha 1 does not officially support Python 3.14. But I don't think we need to do that. And I suppose we don't want to litter this with notes like "added in beta 1" which no one will care about once the final release is there. Then again, we could clean that up after a brief check after any release.
Does it make sense to add a note at the top of the 6.2 upgrade doc saying "This release is not final yet, some of the notes in here may be for a version that is soon to be released." ?
I may be overthinking this. :-)
|
I'd wait for a final release to avoid the need to explain details and adding confusion. Bleeding edge developers already know what's going on, but not the general public. |
Co-authored-by: David Glick <david@glicksoftware.com>
DO NOT MERGE until Plone 6.2 final is released.
@mauritsvanrees here ya go!
Merge plone/volto#8051 before this one, so that I can update its submodule.
📚 Documentation preview 📚: https://plone6--2071.org.readthedocs.build/