Closed mauritsvanrees closed 1 year ago
Let's look at the timing. There are two weeks left in June. Last week of June has two sprints: MidSummer and Cerrado. First week of July I am on vacation. Second week of July is the ArtSprint. So it would be good to prepare Plone 6.0.6 next week, and have it ready in the last week of June.
Note: in July I want to skip Plone 6.0, and only do a 5.2 release. In August we will do a 6.0.7.
cc @tisto @sneridagh @erral @petschki @thet @gforcada
I want to point out one upcoming major change that I want to include in this release: update plone.staticresources/mockup/plonetheme.barceloneta/mosaic to Bootstrap 5.3. See my comments on the coredev PR, starting here. There is a problem with custom themes, but I have seen that this already is a problem with existing or new custom themes simply because Bootstrap 5.3 is available, and will be pulled in automatically if you have no package-lock.json
yet. As far as I see, an existing theme can continue to use Bootstrap 5.2, even when Plone 6.0.6 uses Bootstrap 5.3. We need to document the needed changes, but this is needed regardless of whether we update Plone Classic UI to Bootstrap 5.3 or not.
In the end, it is no breaking change, just a new feature release, like we do new features in Volto and plone.restapi as well.
If you have any thoughts about this, best add them to the coredev PR.
I'll be off during the weekend, so I have just released plone.app.locales = 6.0.15
As far as I see, an existing theme can continue to use Bootstrap 5.2, even when Plone 6.0.6 uses Bootstrap 5.3.
That's correct. Though it's very simple to upgrade to newest @plone/plonetheme-barceloneta-base
with BS 5.3 if you generated a custom theme based on Barceloneta... see this commit which only adds the new dark
variable files and you're good to go: https://github.com/plone/bobtemplates.plone/pull/550/commits/e61c34439582eac2b52fab15327c849a69e6da05
Everything else is basically only color mode features which does not interfere with your Bootstrap 5.2 theme. I'm preparing PRs in bobtemplate.plone
and plonetheme.barceloneta
right now which will document this.
Plone 6.0.6rc1 is available. Announcement: https://community.plone.org/t/plone-6-0-6-soft-released/17595
Plone 6.0.6 is available: https://dist.plone.org/release/6.0.6/
See the release schedule.
Release packages, update versions
bin/manage report --interactive
. This is less needed now that we havemr.roboto
to add packages to the checkouts. Usebin/versioncheck
to see if any new PyPI releases are worth adding, or check the artifact of the versioncheck GitHub Action.checkouts.cfg
.CMFPlone metadata.xml
and latestupgrade step
are in sync, and that they are higher than in the previous Plone release.plone.staticresources
andmockup
. Ask on Discord in the classic-ui or ask Johannes (thet), Peter Mathis (petschki) or Maik (MrTango).plone.restapi
and maybeplone.volto
. If needed, ask the Plone REST api team or Timo (tisto) for a new release.plone.app.locales
. Create an issue there or ask Mikel (erral).plone.app.upgrade
andPlone
yourself.versions.cfg
.Products.CMFPlone
(e.g. 6.0.0a1, later 6.0.0b1 and 6.0.0rc1). Fine to release this on PyPI. Once Plone 6 is final, we can continue doing release candidates for the bugfix releases, so people can try it in a pending release.Release notes, constraints, dist.plone.org
release/6.0-dev
. Most importantly, theauto-checkout
list incheckouts.cfg
should be empty, and theversions.cfg
andrequirements.txt
should be the same. One way that works for me:git checkout release/6.0-dev; git reset --hard 6.0; git reset origin/release/6.0-dev
. Then check which changes you want to commit.6.0-dev
directory on dist.plone.org, and gather files to put there:tox -c release/tox.ini -p auto
to create or copy some files inrelease/dist
. But you need to create some of those files first.bin/manage changelog --start=6.0.0a1 > release/changelog.txt
. Remove the uninteresting top lines. You may want to link to the Zope changelog with a specific tag.release/RELEASE-NOTES.md
. It may be enough to look through the changelog and copy interesting changes.versions.cfg
file and any other versions files from coredev.release/constraints.txt
file from this. The above tox command generates this. Note: at some point I expect the constraints file to become leading, and we may need to generate aversions.cfg
file instead.rsync
) these files to the pending release directory. (We used to copy packages as well, but we do not do this for Plone 6 anymore.)Final release, Docker
Products.CMFPlone
to PyPI, updateversions.cfg
.release/6.0-dev
branch update changelog, release notes,constraints.txt
.release/6.0-dev
branch, e.g. 6.0.0a1, and push to GitHub.ln -sfT 6.0.0a1 6.0-latest
#release-team
Discord channel that there is a new release. They will create Docker images. Examples of changes:README.md
andversion.txt
.Announcements
You probably want to wait until the Docker images are there, but don't wait long.
plone.securitysupport
,plone.versions
,plone.activemaintenance
. You could ask the security team.plone/documentation
'sconf.py
, updatePLONE_BACKEND_PATCH_VERSION
andPLONE_BACKEND_MINOR_VERSION
as needed. Ask Steve Piercy or do it yourself. Here is a sample PR.