After release, Travis CI bin/buidout started bark

[miohtama]

Hi @jaroel ,

After I made 0.13 release, looks like Travis CI is failing in bin/buildout related to pindowns

Getting distribution for 'collective.z3cform.datagridfield[test]==0.13.dev0'.

While:

Installing test.

Getting distribution for 'collective.z3cform.datagridfield[test]==0.13.dev0'.

Error: Couldn't find a distribution for 'collective.z3cform.datagridfield[test]==0.13.dev0'.

Do you know if there are any post-release actions needed to perform in order to make buildout happy again?

[jaroel]

https://github.com/collective/collective.z3cform.datagridfield/blob/master/base.cfg needs to have the development versions specified.
Somehow using 'develop .' or mr.developer does not overrule the pinning in Plone's version.cfg

[jaroel]

Build is fixed.

[miohtama]

Hmm... do we need those pinnings in there in the first place?

[jaroel]

Afaik yes. bin/test does not include the development version, because Plone's version.cfg explicitly pins it.
I think this is a bug, but I haven't read the documentation, so it might be by design :)

[reinout]

@jaroel : add collective.z3cform.datagridfield = to your version list. So an = without a version number. This overrides Plone's pinned version, so buildout will just grab the latest one (in this case the development version).

(See zestsoftware/zest.releaser#41)

[jaroel]

Nice!

[reinout]

Note that there was some debate on the mailinglist about development eggs. Should buildout always use development eggs despite version pins that (explicitly) tell it to use a certain version? I think so. But there was no clear consensus, so the current behaviour ("a pin wins") was left in place.