Closed mauritsvanrees closed 1 year ago
plone.app.locales
release please?I would like to have the releases on Wednesday May 24. Then Thursday/Friday the prerelease, and Tuesday 30 May the final release (Monday is the day after Pentecost).
@petschki @thet I see the extra effort of maintaining one branch of several Classic UI packages for 6.0 and one for 6.1. We could consider allowing Bootstrap 5.3 support in 6.0.x. But let's keep Bootstrap 5.2 as long as 5.3 is still in the alpha phase.
Released plone.app.locales = 6.0.14
Recent releases for Plone 6.0.x (all version files on coredev are up to date)
versions.cfg
plone.staticresources = 2.0.11
plonetheme.barceloneta = 3.0.2
versions-ecosystem.cfg
:
plone.app.standardtiles = 3.1.1
plone.app.mosaic = 3.0.3
npmjs: @plone/mockup = 5.0.12 @plone/plonetheme-barceloneta-base = 3.0.2
Features and bugfixes for Plone 6.1.x moving in parallel but I'm all in for bringing Bootstrap 5.3 to Plone 6.0.x when its final 👍🏼
Thanks for the releases!
Features and bugfixes for Plone 6.1.x moving in parallel but I'm all in for bringing Bootstrap 5.3 to Plone 6.0.x when its final 👍🏼
Let's consider that, yes, if it reduces maintenance burden without introducing breaking changes.
Coredev 6.0 uses fresh Zope 5.8.2 now, instead of a checkout.
A release candidate is almost ready. I have updated https://dist.plone.org/release/6.0-dev/ with the latest versions. No CMFPlone/Plone/p.a.upgrade yet.
But an interesting change was merged in plone.restapi
today: the universal relations service.
@tisto Do we want that in this release? I am happy to wait another day or two.
@sneridagh I am linking to Volto 16.20.6 in the release notes. Are you planning a new Volto 16 release this week? Will any code in Volto 16 use the new restapi endpoint, or will that only be in Volto 17?
@mauritsvanrees we might want to wait for the new p.restapi release. In the Volto Tram meeting we identified maybe a couple of another things mergeable there.
For the moment it would be great to release p.restapi with the relations addition.
Regarding Volto yes, let me take a look at the sprint outcome, and if we want to push for releasing another 16 one.
I have release 6.0.5rc1:
I have made the final releases, including plone.restapi
8.39.1 with an own zcml startup fix.
Available at https://dist.plone.org/release/6.0.5/
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.