On Thu, Feb 16, 2012 at 4:32 PM, Ralf Gommers
ralf.gomm...@googlemail.com wrote:
On Thu, Feb 16, 2012 at 10:20 PM, Thouis (Ray) Jones tho...@gmail.com
wrote:
On Thu, Feb 16, 2012 at 19:25, Ralf Gommers ralf.gomm...@googlemail.com
wrote:
In another thread Jira was proposed as an
On Wed, Feb 15, 2012 at 12:11 PM, Thouis (Ray) Jones tho...@gmail.comwrote:
On Sat, Feb 11, 2012 at 21:54, Fernando Perez fperez@gmail.com
wrote:
On Sat, Feb 11, 2012 at 12:36 PM, Pauli Virtanen p...@iki.fi wrote:
The lack of attachments is the main problem with this transition. It's
On Thu, Feb 16, 2012 at 19:25, Ralf Gommers ralf.gomm...@googlemail.com wrote:
In another thread Jira was proposed as an alternative to Trac. Can you point
out some of its strengths and weaknesses, and tell us why you decided to
move away from it?
The two primary reasons were that our Jira
On Thu, Feb 16, 2012 at 10:20 PM, Thouis (Ray) Jones tho...@gmail.comwrote:
On Thu, Feb 16, 2012 at 19:25, Ralf Gommers ralf.gomm...@googlemail.com
wrote:
In another thread Jira was proposed as an alternative to Trac. Can you
point
out some of its strengths and weaknesses, and tell us why
How to people feel about moving the issue tracking for NumPy to Github?It
looks like they have improved their issue tracking quite a bit and the workflow
and integration with commits looks quite good from what I can see.
Here is one tool I saw that might help in the migration:
On Saturday, February 11, 2012, Travis Oliphant tra...@continuum.io wrote:
How to people feel about moving the issue tracking for NumPy to Github?
It looks like they have improved their issue tracking quite a bit and the
workflow and integration with commits looks quite good from what I can see.
11.02.2012 20:44, Travis Oliphant kirjoitti:
How to people feel about moving the issue tracking for NumPy to Github?
It looks like they have improved their issue tracking quite a bit and
the workflow and integration with commits looks quite good from what I
can see.
The lack of
This is good feedback.
It looks like there are 2 concerns:
1) no way to add attachments --- it would seem that gists and indeed
other github repos solves that problem.
2) You must be an admin to label an issue (i.e. set it as a bug,
enhancement, or so forth).
This second
On Sat, Feb 11, 2012 at 1:44 PM, Travis Oliphant tra...@continuum.iowrote:
This is good feedback.
It looks like there are 2 concerns:
1) no way to add attachments --- it would seem that gists and indeed other
github repos solves that problem.
2) You must be an admin to label an issue (i.e.
On Sat, Feb 11, 2012 at 12:36 PM, Pauli Virtanen p...@iki.fi wrote:
The lack of attachments is the main problem with this transition. It's
not so seldom that numerical input data or scripts demonstrating an
issue come useful. This is probably less of an issue for Numpy than for
Scipy, though.
On 2/11/12 1:44 PM, Travis Oliphant wrote:
How to people feel about moving the issue tracking for NumPy to Github?
It looks like they have improved their issue tracking quite a bit and
the workflow and integration with commits looks quite good from what I
can see.
Here is one tool I saw that
I think that migration will require some amount of manual intervention, and
that this is a perfect opportunity to review the issues which can be part of
the NumPy 1.8 work-load.
There is an intern I am working with who is looking for something more
substantial to do, and this would also be
11.02.2012 22:02, Jason Grout kirjoitti:
[clip]
Are there any good github trac plugins? For example:
http://davglass.lighthouseapp.com/projects/21212/home
http://trac-hacks.org/wiki/GitPlugin (git, not github, but still maybe
useful)
The Numpy Scipy Trac is currently running on this:
On 02/11/2012 10:44 AM, Travis Oliphant wrote:
This is good feedback.
It looks like there are 2 concerns:
1) no way to add attachments --- it would seem that gists and indeed
other github repos solves that problem.
Not really, in practice. Yes one can use these mechanisms, but they are
On 2/11/12 3:12 PM, Eric Firing wrote:
A third problem is that the entire style of presentation is poorly
designed from a use standpoint, in comparison to the sourceforge tracker
which mpl used previously. The github tracker appears to have been
designed by a graphics person, not a software
On Sat, Feb 11, 2012 at 3:12 PM, Eric Firing efir...@hawaii.edu wrote:
On 02/11/2012 10:44 AM, Travis Oliphant wrote:snip
2) You must be an admin to label an issue (i.e. set it as a bug,
enhancement, or so forth).
A third problem is that the entire style of presentation is poorly
On Sat, Feb 11, 2012 at 9:49 PM, Mark Wiebe mwwi...@gmail.com wrote:
On Sat, Feb 11, 2012 at 3:12 PM, Eric Firing efir...@hawaii.edu wrote:
On 02/11/2012 10:44 AM, Travis Oliphant wrote:snip
2) You must be an admin to label an issue (i.e. set it as a bug,
enhancement, or so forth).
A
17 matches
Mail list logo
