Using zest.release in combination with git-flow about zest.releaser HOT 7 CLOSED

I looked at git flow once and thought it to be utter overkill for my usecases. But it surely has its uses :-)

Would a different kind of tag work? Otherwise a switch somewhere might be needed.

Have you looked at the entry point extension mechanism? You could plug in custom actions that way. You could get something really polished that way in combination with what git flow offers.

from zest.releaser.

(Looking through old issues...)

Yep, I still think an extension to deal with git-flow's alternative tag mechanism would be best. Otherwise zest.releaser's code probably gets too if/else-like. I don't know git-flow well enough to see an alternative at the moment (though there might be).

from zest.releaser.

👍 for supporting the git-flow workflow. We at PyInstaller are preparing the release on a release-branch, tag the releases on master and merge back to develop.

There also is a pure-python implementation of gitlow which eases the process. Creating a release branch is as easy as (leaving of error handling):

    gitflow = GitFlow()
    gitflow.start_transaction('create release branch %s' % version)
    branch = gitflow.create('release', version, base)

If you need assistance, feel free to drop me a note.

from zest.releaser.

This still looks like something that is best done in an extra package that uses the zest.releaser entry points.

from zest.releaser.

Meanwhile it came to my mind that zesz.releaser can be easily incorperated into the git flow release process: simply use prerelease , release and postrelease each by it's own.

from zest.releaser.

I'm closing this old issue as I'm getting the impression that it can be worked out in git flow itself.

from zest.releaser.

You can use egg.releaser which is a wrapper around zest.releaser. Initially created by Thijs in https://github.com/virtualsciences/egg.releaser and forked by me in https://github.com/zestsoftware/egg.releaser

I am sometimes using that for the same client that issue creator @jjmurre may already be using it for. :-) We want to switch away from git flow there though, as most of the team is not used to it. (Me neither, though it works okay.)

from zest.releaser.