That's ... even stranger. I'm sure that I've only merged changes into "next"
from the "0.25.x" and "master" branches.
And it looks to me that my patch successfully made it into the 2.6.0
release. What version are you patching against, Marc?
As of today, "2.6.x" exists as a fork of "master"
"next" will become a staging zone for commits that will eventually their way
into "master" which will eventually become the next major release ("statler"
or "2.7.0" or "27.0")
~Jesse
On Thu, Jul 22, 2010 at 6:27 AM, Marc Fournier <[email protected]
> wrote:
>
> > > +1. I could have sworn we had already caught these, but I guess not.
> >
> > If you're crazy, we both are. I'd also swear we fixed them.
>
> Well it seems nobody is crazy in fact. It indeed got removed by Jesse
> in dc1a977, which is only in the branch called "next".
>
> This makes me wonder how the 0.25.x and older branches relate with the
> "next" branch ?
>
> It would be nice if bugs fixed in one branch get applied to the other
> relevant ones. Easier said than done, I can imagine :-) Shouldn't there
> be a way in redmine to indicate that an issue affects several branches ?
>
> By the way, is it planned to rename the "next" branch to something like
> "2.6.x" now that 2.6.0 is released ?
>
> Cheers,
> Marc
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Developers" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<puppet-dev%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/puppet-dev?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
