On Mon, Apr 2, 2012 at 11:35 PM, Travis Oliphant wrote:
> Sorry, I saw the cross-posting to the NumPy list and wondered if we were
> on the same page.
>
> I don't know of any plans to migrate SciPy Trac at this time: perhaps
> later.
>
> At this time maybe, but I was assuming that if the Numpy m
Sorry, I saw the cross-posting to the NumPy list and wondered if we were on
the same page.
I don't know of any plans to migrate SciPy Trac at this time: perhaps later.
Thanks for the clarification.
Best,
-Travis
I don'tOn Apr 2, 2012, at 3:58 PM, Pauli Virtanen wrote:
> Hi,
>
> 02.0
Hi,
02.04.2012 22:47, Travis Oliphant kirjoitti:
> The plan is use a different issue tracker.
> We are trying out YouTrack right now and hope to
> export the Trac database into YouTrack.
Certainly, I'm aware :)
However, was the plan to also migrate the Scipy Trac? I understood the
answer to t
The plan is use a different issue tracker. We are trying out YouTrack right
now and hope to export the Trac database into YouTrack.
-Travis
the plOn Apr 2, 2012, at 3:16 PM, Pauli Virtanen wrote:
> 31.03.2012 18:19, Pauli Virtanen kirjoitti:
>> I moved projects.scipy.org Tracs to run on mo
31.03.2012 18:19, Pauli Virtanen kirjoitti:
> I moved projects.scipy.org Tracs to run on mod_python (instead of CGI),
> in order to try to combat the present performance issues. Let's see if
> this helps with the "database is locked" problem.
>
> Please drop me a message if something stops working
Hi,
I moved projects.scipy.org Tracs to run on mod_python (instead of CGI),
in order to try to combat the present performance issues. Let's see if
this helps with the "database is locked" problem.
Please drop me a message if something stops working.
Pauli
___
