On Jan 17, 2009, at 7:17 PM, Paul Nasrat wrote: > >>> Any chance we can break this out into functions a bit more, I know >>> it's just the rakefile and helper stuff but it's a long block. >> >> Sure - I just copied the task from the Puppet Rakefile - because I >> use >> it there. > > >>> So I'm guessing that we need to do say: >>> >>> feature/master/win32 which seems a little verbose - is that right? >> >> It's the format we choose for Puppet - happy to entertain >> alternatives. > > OK, so I'd just have some helper tasks to do the branching for ppl, > it'll ensure consistency - I think I've varied between ticket/ and > tickets/ on facter before and it's just easier if I don't have to > think. I guess as master is a concept rather than a tracked version we > might actually want to put target version in there. How are ppl > finding using the helpers?
I prefer to have the parent branch in the branch name. It used to make sense to have some kind descriptor in there, like, feature or bug, but really, tickets/<parent branch>/<ticket_number> seems appropriate and sufficient. > > Dunno if redmine has a REST, XML-RPC or whatever interface to create > issues but we could do that too. What would we use this for, again? Did I miss something? -- Nothing is impossible for the man who doesn't have to do it himself. -- A. H. Weiler --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
