Closed mauritsvanrees closed 1 year ago
@tisto @erral @thet @petschki Could I have releases of your packages please? I would like them by next Wednesday, April 19. Release candidate on Thursday 20 or Friday 21. Final release on Monday 24.
@gforcada If you want to create releases of other packages, that would be nice.
Thanks in advance all!
Released plone.app.locales = 6.0.13
@mauritsvanrees only plone.locking
is missing a release.
I want to wait to get https://github.com/plone/plone.locking/pull/23 merged.
@mauritsvanrees I merge and release https://github.com/plone/plone.staticresources/pull/280 now ... hopefully not too late
@petschki Thanks, that is fine. I saw a CMFPlone PR from @thet about Tinymce plugins. Could you check if that makes sense?
sure ... made sense. I've merged it.
staticresources and barceloneta are ready for Plone 6.0.4
Thanks all! Plone 6.0.4rc1 is there. See announcement.
And @fredvd and me recorded it for World Plone Day. One and a half hours of material. :-)
This weekend and today I have updated the version of plone.app.standardtiles to 3.0.1 and plone.app.mosaic to 3.0.2. Both ecosystem packages. The release is final now:
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
#install-and-deploy
Discord channel, that there is a new release. He can create Docker images then.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.