Plone 5.1a1 soft-released

Plone 5.1a1 has been soft-released. Please give it a try and let me know if there are any critical issues.

For those who haven't run across soft-releases before, this is the
last step before the final release. Because things haven't been
finalized yet, some packages may change between now and the release. It
is not recommended to use soft-releases in production.


1 Like

Thanks @esteele!

I got a conflict with ExtensionClass.

We are depending on ExtensionClass = 4.1.2 but Products.MailHost and
Products.BTreeFolder2 have a dependency on ExtensionClass < 4.0. This is
fixed in their master branches. The difference to the branches, we are
referring to in sources.cfg is only that they removed this conflicting
version fix.

I have created a pull request. The Jenkins job is currently running.

What are the improvements in 5.1a1? Any significant improvements to the various JS/CSS resource registry problems and deficiencies?


can we take this list as the expected goal of this release?

given the state of things, I would suggest to deprecate maintenance on 5.0 branch and keep alive 4.3.

I'll get a change list together. My script doesn't work so well for minor releases.

Once 5.1 is stable (which shouldn't take long since its a relatively small featureset), we'll discontinue the 5.0.x releases.

4.3.x will continue until 6.0 is released.


@esteele just to let you know that I'm not being able to test under Plone 5.1a1; seems some sort of headers problem:

UPDATE: I re-run the build and lost the log; but I have another build with the same issue just as a reference:

The problem was fixed: I have now 3 add-ons with tests passing on Plone 5.1.

how about a new alpha?

we need a new classifier in PyPI for Plone 5.1, also.