Re: [matplotlib-devel] New issue tracker on GitHub

2011-04-14 Thread Darren Dale
On Mon, Apr 11, 2011 at 3:51 PM, Eric Firing wrote: > On 04/11/2011 07:24 AM, Darren Dale wrote: >> On Mon, Apr 11, 2011 at 12:13 PM, Michael Droettboom  wrote: >>> I couldn't find the old thread about Sourceforge bug tracker vs. the >>> Github issue tracker, but maybe we should reevaluate based o

Re: [matplotlib-devel] New issue tracker on GitHub

2011-04-12 Thread Fernando Perez
On Mon, Apr 11, 2011 at 2:19 PM, Darren Dale wrote: > > Brilliant, whatever they use allows uploading attachments. I know this isn't ideal, but a workaround for screenshots/images in mpl bug reports would be to upload them to something like imgur (free - no registration required): http://imgur.c

Re: [matplotlib-devel] New issue tracker on GitHub

2011-04-11 Thread Eric Firing
On 04/11/2011 11:19 AM, Darren Dale wrote: > On Mon, Apr 11, 2011 at 3:40 PM, Michael Droettboom wrote: >> (Hmm... git doesn't use its own issue tracker for tracking its own >> issues... what does that say?) > > Brilliant, whatever they use allows uploading attachments. They are using this: http:

Re: [matplotlib-devel] New issue tracker on GitHub

2011-04-11 Thread Benjamin Root
On Mon, Apr 11, 2011 at 4:19 PM, Darren Dale wrote: > On Mon, Apr 11, 2011 at 3:40 PM, Michael Droettboom > wrote: > > (Hmm... git doesn't use its own issue tracker for tracking its own > > issues... what does that say? ) > > Brilliant, whatever they use allows uploading attachments. > > Maybe i

Re: [matplotlib-devel] New issue tracker on GitHub

2011-04-11 Thread Darren Dale
On Mon, Apr 11, 2011 at 3:40 PM, Michael Droettboom wrote: > (Hmm... git doesn't use its own issue tracker for tracking its own > issues... what does that say? ) Brilliant, whatever they use allows uploading attachments. ---

Re: [matplotlib-devel] New issue tracker on GitHub

2011-04-11 Thread Michael Droettboom
On 04/11/2011 03:51 PM, Eric Firing wrote: > On 04/11/2011 07:24 AM, Darren Dale wrote: > >> On Mon, Apr 11, 2011 at 12:13 PM, Michael Droettboom >> wrote: >> >>> I couldn't find the old thread about Sourceforge bug tracker vs. the >>> Github issue tracker, but maybe we should reevalua

Re: [matplotlib-devel] New issue tracker on GitHub

2011-04-11 Thread Eric Firing
On 04/11/2011 07:24 AM, Darren Dale wrote: > On Mon, Apr 11, 2011 at 12:13 PM, Michael Droettboom wrote: >> I couldn't find the old thread about Sourceforge bug tracker vs. the >> Github issue tracker, but maybe we should reevaluate based on the new >> Github issue tracker announced on Saturday: >

Re: [matplotlib-devel] New issue tracker on GitHub

2011-04-11 Thread Darren Dale
On Mon, Apr 11, 2011 at 3:02 PM, Paul Ivanov wrote: > Darren Dale, on 2011-04-11 13:24,  wrote: >> On Mon, Apr 11, 2011 at 12:13 PM, Michael Droettboom wrote: >> > I couldn't find the old thread about Sourceforge bug tracker vs. the >> > Github issue tracker, but maybe we should reevaluate based

Re: [matplotlib-devel] New issue tracker on GitHub

2011-04-11 Thread Paul Ivanov
Darren Dale, on 2011-04-11 13:24, wrote: > On Mon, Apr 11, 2011 at 12:13 PM, Michael Droettboom wrote: > > I couldn't find the old thread about Sourceforge bug tracker vs. the > > Github issue tracker, but maybe we should reevaluate based on the new > > Github issue tracker announced on Saturday:

Re: [matplotlib-devel] New issue tracker on GitHub

2011-04-11 Thread Darren Dale
On Mon, Apr 11, 2011 at 12:13 PM, Michael Droettboom wrote: > I couldn't find the old thread about Sourceforge bug tracker vs. the > Github issue tracker, but maybe we should reevaluate based on the new > Github issue tracker announced on Saturday: > > https://github.com/blog/831-issues-2-0-the-ne