I'm a bit +1 to this idea. I've been trying to mentally juggle the list of outstanding bugs in branches, and that doesn't work out too well. Having a ticket to keep track of issues in a branch that is intended to be merged would be a very big help for some of the more complicated branches.
--Andrew Whitworth On Sat, Sep 29, 2012 at 11:50 AM, Jonathan "Duke" Leto <[email protected]> wrote: > Howdy, > > I propose that we start using Github issues for bugs in branches, > especially those in important branches that we are actively trying to > merge (like threads). > > Just make sure to clearly state in the issue that the bug applies to a > branch. If anybody thinks this is a horrible idea, please speak up. > > And conversely, if you know of bugs on the threads branch, please > create an issue for it. > > Duke > > -- > Jonathan "Duke" Leto <[email protected]> > Leto Labs LLC http://labs.leto.net > 209.691.DUKE http://dukeleto.pl > _______________________________________________ > http://lists.parrot.org/mailman/listinfo/parrot-dev _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
