-
-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plone 5.2.2 release checklist #3119
Comments
I'm going to create a list of known i18n issues here #3123 |
I consider those issues as blockers
|
Here is a full list of issues marked as 'blocker' in the whole Plone organisation. And 82 are marked as regressions, the oldest being from myself in 2013. |
All releases for a 5.2.2-pending have been made, most importantly CMFPlone 5.2.2rc1. I have created a coredev branch release-5.2.2-pending with an empty I have created https://dist.plone.org/release/5.2.2-pending/ with at the moment only the |
I have uploaded the packages to https://dist.plone.org/release/5.2.2-pending/ Note to self, to gather all packages, edit a buildout config file in coredev (I used
This counters the shared directories I have specified in Then run At the end, or in between, Note that when I do this, I get a few Mac OSX specific wheels:
It would be nicer to only have the source distributions ( |
Thank you for your hard work making the releases! |
Thanks, I have included it. |
I spotted a breaking change that is fixed by plone/plone.app.layout#240 |
I would also add #3135 as a blocker. |
I made various i18n fixes in the following packages, it would be great to have those fixes in Plone 5.2.2.
|
Blockers: Nice to have:
Further, we will want new releases of:
I can see the danger of including more and more changes and then never actually finishing the release... |
Blockers:
A message was not internationalized for the new Custom CSS feature:
|
plone/plone.dexterity#126 is not a blocker anymore For chameleon #3135 discussion is ongoing. I'm releasing a last version of plone.app.locales tomorrow morning CET. |
At this point, I don't feel comfortable making 5.2.2 final with Zope 4.4.4. There are too many reports of template problems. |
This is your call! And I would trust your instincts. Have a great vacation week celebrating Canada Day! 🇨🇦 😆 |
Have a great vacation! |
I have updated https://dist.plone.org/release/5.2.2-pending Remaining known issues:
|
With my Security Team hat on I want this in, to ease future hotfixes:
With my Release Manager hat on, I grumble about this, but grudgingly agree. |
New one about dependencies, should be easy to fix: |
|
I have done a couple more releases, some fixing issues mentioned above, plus some small bug fixes. |
ZEO and Zope releases are available, changes merged to coredev. |
I have made release candidate 5.2.2rc3: |
And 5.2.2 is final! Now I need to get back to my earliest checklist above. |
Note that based on coredev branch release-5.2.2-pending I have made tag 5.2.2. |
|
As one of the release managers, I want to make releases for Plone 4.3, 5.1, and 5.2 in June 2020. See also the release schedule. First up is Plone 5.2.2.
As an experiment, I want to have the status available with a checklist in an issue on GitHub, so people can follow along. From here we can link to issues that are blockers. Ultimately, it is a decision from the release team to say if an issue is really a blocker or not. But feel free to tag an issue as blocker, and link it here in a comment.
Another idea is that I create a
buildout.coredev
branchrelease-5.2.2-pending
(or similar) with an emptycheckouts.cfg
once the package releases are done and a pending release is available on dist.plone.org. If any further releases are needed, based on feedback, I can update this branch. Once the release is final, I will create a 5.2.2 tag.So here is the checklist, based on https://docs.plone.org/develop/coredev/docs/release.html (see source):
bin/manage report --interactive
checkouts.cfg
.CMFPlone metadata.xml
and latestupgrade step
are in sync.mockup
andplone.staticresources
are in sync and can be released.plone.restapi
andplone.rest
.plone.app.locales
version.Products.CMFPlone
and put it only on dist.plone.org, not PyPI.bin/manage changelog
Products.CMFPlone
to PyPIbin/manage launchpad <version>
plone.securitysupport
,plone.versions
,plone.activemaintenance
)The text was updated successfully, but these errors were encountered: