Bug #59586 for Dist-Zilla-Plugin-Git: releases branch

Wed Jul 21 01:01:51 2010 xenoterracide [...] gmail.com - Ticket created

CC:	xenoterracide [...] gmail.com
Subject:	releases branch

where'd this come from? how do I get rid of it? I don't want it, is it necessary?

Wed Jul 21 02:37:46 2010 jquelin [...] cpan.org - Correspondence added

it comes from: 1.101800 2010-06-29 18:36:17 Europe/Paris - git::commitbuild - new release_branch option to commit result after a release (yanick champoux) now, if you're using this plugin in your dist.ini, with a release_branch option, you get a release branch. to get rid of it: remove the commitbuild plugin, or remove the release_branch option. in any case, commitbuild plugin is not activated in @git. ==> i don't really understand how you could get this behaviour without specifying it. rejecting bug, but reopen if i misunderstood.

Wed Jul 21 02:37:46 2010 The RT System itself - Status changed from 'new' to 'open'

Wed Jul 21 02:37:47 2010 jquelin [...] cpan.org - Status changed from 'open' to 'rejected'

Wed Jul 21 02:48:43 2010 xenoterracide [...] gmail.com - Correspondence added

Show quoted text

> to get rid of it: remove the commitbuild plugin, or remove the > release_branch option. in any case, commitbuild plugin is not

activated Show quoted text

> in @git.

I don't know either. as you've seen in my other bug... [@Git] push_to = my tag_format = %v [Git::CommitBuild] that's it for my git options. Show quoted text

> ==> i don't really understand how you could get this behaviour without > specifying it. rejecting bug, but reopen if i misunderstood.

I've never added a release_branch option.

Wed Jul 21 02:48:44 2010 The RT System itself - Status changed from 'rejected' to 'open'

Wed Jul 21 03:01:11 2010 jquelin [...] cpan.org - Correspondence added

ok, found it: release_branch had a default value. fixed in 1.102020

Wed Jul 21 03:01:11 2010 jquelin [...] cpan.org - Status changed from 'open' to 'resolved'