Its not really a tick against using it, I like the openness and integration. Its more of a 'be aware of the additional overhead' kind of thing.
On Mon, Apr 11, 2011 at 9:39 AM, Jordan Wilberding <[email protected]> wrote: > Hmm.. maybe we could suggest to github they allow issue tracking for > "Organizations". > On Mon, Apr 11, 2011 at 10:35 AM, Eric Merritt <[email protected]> > wrote: >> >> One thing we are going to need to be aware of is that right now in >> pivitol we manage our projects together, we wont be able to do that >> using this approach. >> >> On Sun, Apr 10, 2011 at 9:23 AM, Jordan Wilberding >> <[email protected]> wrote: >> > Maybe we should transition to this from Pivotal? >> > https://github.com/blog/831-issues-2-0-the-next-generation >> > Thanks! >> > Jordan Wilberding >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups >> > "erlware-dev" 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/erlware-dev?hl=en. >> > > > -- You received this message because you are subscribed to the Google Groups "erlware-dev" 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/erlware-dev?hl=en.
