Use 6-latest for the truly latest 6

[stevepiercy]

• Thus we don't have to update it for 6.2 🥳

---

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

[davisagli]

No, please don't do that. Getting patch releases automatically is probably a good thing. Getting minor updates with new features without opting into it is too surprising.

[stevepiercy]

@davisagli the context is for install only, so I don't understand your comment. If I install Plone, I expect the latest possible versions. Can you elaborate?

[davisagli]

@stevepiercy I was overlooking the context of where you changed it. It should be okay to use 6-latest in these places. I wouldn't want to use it in the buildout instructions, since the buildout could be re-run in the future and we wouldn't want an accidental upgrade at that point.

[stevepiercy]

@davisagli OK, yeah, that's what I had in mind. There are some places I didn't change, for example in the version upgrade guides or this:

documentation/docs/install/create-project.md

Line 196 in d633bbb

For {guilabel}`Project Slug`, you must not use any of the Plone core package names listed in [`constraints.txt`](https://dist.plone.org/release/6.0-latest/constraints.txt).

Or updating documentation's own requirements to avoid those unwanted surprises.

https://github.com/plone/documentation/pull/1845/files#diff-54c8b05644cf835f41801972f716dfd4eb526ae9be79c33297be600dfeb7c259

I tried to keep the context in mind when doing these recent updates, but it's possible I goofed.