On Wed, Jul 25, 2012 at 7:36 PM, Ralf Gommers
wrote:
> [...]
> It looks like you want to discard the Milestones, except for the 1.7.0,
> 1.8.0 and 2.0.0 ones. Why not keep all of them?
These were the only ones defined in the current numpy repository.
I'll add code to create any missing ones.
> I
On Wed, Jul 25, 2012 at 3:51 AM, Thouis (Ray) Jones wrote:
> On Wed, Jul 25, 2012 at 6:53 AM, Fernando Perez wrote:
>> Hi Thouis,
>>
>> On Tue, Jul 24, 2012 at 2:46 PM, Thouis (Ray) Jones wrote:
>>> I would estimate I'm between a fourth and halfway through the
>>> implementation of the trac-to-g
On Tue, Jul 24, 2012 at 11:46 PM, Thouis (Ray) Jones wrote:
> Hello,
>
> I would estimate I'm between a fourth and halfway through the
> implementation of the trac-to-github-issues migration code. The work
> lives in at https://github.com/thouis/numpy-trac-migration , though
> without a copy of t
On Wed, Jul 25, 2012 at 6:53 AM, Fernando Perez wrote:
> Hi Thouis,
>
> On Tue, Jul 24, 2012 at 2:46 PM, Thouis (Ray) Jones wrote:
>> I would estimate I'm between a fourth and halfway through the
>> implementation of the trac-to-github-issues migration code. The work
>> lives in at https://githu
Hi Thouis,
On Tue, Jul 24, 2012 at 2:46 PM, Thouis (Ray) Jones wrote:
> I would estimate I'm between a fourth and halfway through the
> implementation of the trac-to-github-issues migration code. The work
> lives in at https://github.com/thouis/numpy-trac-migration
mmh, I would have thought you
Hello,
I would estimate I'm between a fourth and halfway through the
implementation of the trac-to-github-issues migration code. The work
lives in at https://github.com/thouis/numpy-trac-migration , though
without a copy of the trac DB, it's not really possible to experiment
with it. I haven't i
