On Wed, Jul 14, 2010 at 8:10 PM, Wyatt Baldwin <[email protected]> wrote: > On Jul 14, 7:15 pm, BrianTheLion <[email protected]> wrote: >> Apologies for my lack of familiarity with the development process on >> the Pylons project, but if somebody will tell me what needs to happen >> to get this "fixed" - whether it's file a bug report, edit and submit >> some code, or just quit whining - I'll be happy to move this issue >> forward. Cheers! ~br > > I submitted a patch to Routes once. It went something like this > (although the repo was Subversion back then): > > Go to http://bitbucket.org/bbangert/routes and clone the repository. > Make the change on your clone and make sure the existing tests still > pass. Add a new test to test the new behavior. Submit a pull request. > > I guess you could add an issue, too, but it's a pretty small change, > so I'm not sure that's necessary. > > Anyway, that's what approximately I would do.
A ticket makes it easiest to manage the issue, so that it remains on the todo list until it's done. You can either clone the repository and make the change, or describe what needs to be done, or if you don't know how to implement it just describe what you want. -- Mike Orr <[email protected]> -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
