Update zope branches in sources.cfg. [5.2]

plone / buildout.coredev

Plone Core Development Buildout

http://docs.plone.org/develop/coredev/docs/

74 stars 75 forks source link

Update zope branches in sources.cfg. [5.2] #841

Closed mauritsvanrees closed 1 year ago

mauritsvanrees commented 1 year ago

A lot of master branches are being updated to drop Python 2.7 support, so we want maintenance branches. I removed several source definitions that were duplicate from the one in Zope/sources.cfg, or that are really not used anymore, like five.pt and ZODB3. I am updating the Zope 4.x sources.cfg as well, and don't want to do this in two places. Related PR, which would best be merged first: https://github.com/zopefoundation/Zope/pull/1099

I will make the coredev PR a draft PR for now.

gforcada commented 1 year ago

Sounds like a good idea to rely on zope for their sources configuration 👍🏾

Doesn't that go at odds with the idea of having requirements.txt leading (i.e. pip based workflow) rather than versions.cfg ? 🤔

Or is it irrelevant? 😅

mauritsvanrees commented 1 year ago

This PR is for Plone 5.2. I am not planning to make requirements.txt the canonical place there.

I have merged my Zope PR, so we can test now on Jenkins, although it should not have an influence as long as we do not checkout any further packages.

@jenkins-plone-org please run jobs