On Fri, 2010-03-19 at 07:41 -0700, Markus Roberts wrote: > Brice -- > > Though I've been quiet on this thread I've been following it with > interest.
Too bad, your comments are always insightful, and you might have some clever idea to fix the aforementioned issue. > I have two favors to ask: > > * Since we appear agreed the previous patch is a Good Thing, even if > it's not the ultimate solution to everything, could you put it in a > branch, add it to the ticket, and mark it "Ready for Testing" The branch is currently against 0.25.x, should I create a new one against master and/or testing? > * Could you open a new ticket for the forthcoming more general fix, > and do the same with that change as soon as it's available? Will do. > I'm trying to get all the things the we'd like to see in Rowlf rolled > into the testing branch in the next week, so we can bang them against > each other. OK, I understand. More generally, if, say, I want to produce a new patch for Rowlf (I'm thinking about some random puppetdoc fix or feature), what is the more convenient for you: * base it on top of the latest available testing (or somewhere in the middle) * base it on master Thanks, -- Brice Figureau Follow the latest Puppet Community evolutions on www.planetpuppet.org! -- 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.
