Feature request: Check if version is already available about zest.releaser HOT 6 CLOSED

On 06-06-12 16:39, mat wrote:

• Check if package/version already exists on repository (pypi, plone.org, etc.)
• Check if tag already exists in code repo (git/svn)

The tag-checking already happens. It actually was one of the first
features to go in :-)

And I think the first one isn't really needed. If the first one applies,
the second one will already have warned you, right?

Reinout

Reinout van Rees [email protected]
http://reinout.vanrees.org/
"Military engineers build missiles. Civil engineers build targets."

from zest.releaser.

We already check if the package is on PyPI. If it is there, we switch the default answer for uploading the package to PyPi to False. For plone.org there is currently no official api that we can use to check this.

If this specific version is already on PyPI then you or another package maintainer has apparently done something weird already and we get into corner cases where we happily allow you to shoot yourself in the foot. ;-)

from zest.releaser.

Thanks for your responses.

If this specific version is already on PyPI then you or another package maintainer has apparently done something weird already...

This is exactly what happens from time to time. Although github gives you nice possibilities to fork code, make pull requests, etc... your are not aware of (for example) someone makes a new release out of a branch. Usually you should now the guy(s) who did this. But I just thought it would bi nice if zest.releaser could print out something like "ooops you're overwriting an existing release on pypi". Of course this should no happen and yes your right, there's blood everywhere, but not mine :-)

from zest.releaser.

On 07-06-12 17:25, mat wrote:

If this specific version is already on PyPI then you or another package maintainer has apparently done something weird already...
This is exactly what happens from time to time. Although github gives you nice possibilities to fork code, make pull requests, etc... your are not aware of (for example) someone makes a new release out of a branch. Usually you should now the guy(s) who did this. But I just thought it would bi nice if zest.releaser could print out something like "ooops you're overwriting an existing release on pypi". Of course this should no happen and yes your right, there's blood everywhere, but not mine:-)

But still... If someone else already made a release, the change should
also be in your checkout: a new changelog header, a new version.

The only scenario I can think off is if you're all working in different
branches and releasing from that independently. But that means different
releases are based on different codebases....

You'll really have to have one main branch and then zest.releaser will
warn you properly.

Reinout

Reinout van Rees [email protected]
http://reinout.vanrees.org/
"Military engineers build missiles. Civil engineers build targets."

from zest.releaser.

But that means different releases are based on different codebases....

Unfortunately that's what could happen accidentally. But you're right this scenario must be handled by the developer.
So I close this issue, thanks again!

from zest.releaser.

On 07-06-12 19:20, mat wrote:

But that means different releases are based on different codebases....
Unfortunately that's what could happen accidentally. But you're right this scenario must be handled by the developer.
So I close this issue, thanks again!

Ok. Good luck educating them :-)

Reinout

Reinout van Rees [email protected]
http://reinout.vanrees.org/
"Military engineers build missiles. Civil engineers build targets."

from zest.releaser.