Closed mauritsvanrees closed 1 month ago
With plone.app.discussion
being a core add-on since today, a new release is welcome, so that part can get more testing in the real world.
@tisto @sneridagh @petschki @erral Please make releases where needed. I would like to have those this Wednesday, September 4. Then I can make a release the next day.
Released plone.app.locales = 6.0.24
latest releases:
plone.staticresources = 2.2.0a10
plonetheme.barceloneta = 3.2.0a6
npm
@plone/mockup = 5.2.0-alpha.10
@plone/plonetheme-barceloneta-base = 3.2.0-alpha.6
Thanks for the releases. I have released Plone 6.1.0a5: https://dist.plone.org/release/6.1.0a5/ Announcements on plone.org and community.plone.org to follow tomorrow.
All done.
With
plone.app.discussion
being a core add-on since today, a new release is welcome, so that part can get more testing in the real world.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.1.0a1, later 6.1.0b1 and 6.1.0rc1). Fine to release this on PyPI. Once Plone 6.1 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.1-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.1-dev; git reset --hard 6.1; git reset origin/release/6.1-dev
. Then check which changes you want to commit.6.1-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.1.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.1-dev
branch update changelog, release notes,constraints.txt
.release/6.1-dev
branch, e.g. 6.1.0a1, and push to GitHub.ln -sfT 6.1.0a1 6.1-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.