Well, I just noticed something that could be a problem. GitHub uses the same numbering scheme for pull requests and issues. This means that pull request 42 is also considered to be issue 42. For example, see the issues for the website: https://github.com/sympy/sympy.github.com/issues. Issue #24 is an actual issue that I just created. Issues 1-23 are actually pull requests 1-23.
It also means that they consider pull requests to *be* issues, which is a little different from how we have been treating them (for example, we can close pull requests and reopen them, but issues should only be closed when they are fixed). Aaron Meurer On Apr 30, 2011, at 7:37 AM, Vinzent Steinberg wrote: > On Apr 30, 12:42 am, "Aaron S. Meurer" <[email protected]> wrote: >> Technically, Google Code has a better tag system, because it lets you have >> tags like our Priority, Status, and Type that can only take one value per >> issue. > > Yeah, multi-value labels are lacking. > >> Also, the default labels functionality doesn't seem to be as strong. It >> also doesn't seem to have the ability to automatically do things based on >> labels (like in Google Code, we send updates of issues with the review >> labels to the patches list). > > Provided they have a good API, this could be easily done by sympy-bot. > Also we wouldn't need it, because on github pull request are tied > closely enough with the issues. Everyone who wants an email can tell > github to send one for every pull request. > > Vinzent -- You received this message because you are subscribed to the Google Groups "sympy" 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/sympy?hl=en.
