On Tue, Oct 23, 2012 at 8:57 PM, Thouis (Ray) Jones wrote:
> On Tue, Oct 23, 2012 at 10:58 AM, David Cournapeau wrote:
>> I will look into making the NumPy trac read-only. It should not be too
>> complicated to extend Pauli's code to redirect the tickets part to
>> github issues.
>
> If you need
On Tue, Oct 23, 2012 at 10:58 AM, David Cournapeau wrote:
> I will look into making the NumPy trac read-only. It should not be too
> complicated to extend Pauli's code to redirect the tickets part to
> github issues.
If you need the map of trac IDs to github IDs, I have code to grab that.
Ray
__
On Tue, Oct 23, 2012 at 5:13 PM, Travis Oliphant wrote:
>
> On Oct 23, 2012, at 9:58 AM, David Cournapeau wrote:
>
> > On Tue, Oct 23, 2012 at 5:05 AM, Thouis (Ray) Jones
> wrote:
> >> On Fri, Oct 19, 2012 at 9:34 PM, Thouis (Ray) Jones
> wrote:
> >>> On Fri, Oct 19, 2012 at 4:46 PM, Thouis (Ray
On Oct 23, 2012, at 9:58 AM, David Cournapeau wrote:
> On Tue, Oct 23, 2012 at 5:05 AM, Thouis (Ray) Jones wrote:
>> On Fri, Oct 19, 2012 at 9:34 PM, Thouis (Ray) Jones wrote:
>>> On Fri, Oct 19, 2012 at 4:46 PM, Thouis (Ray) Jones
>>> wrote:
On Fri, Oct 19, 2012 at 11:20 AM, Thouis (Ray
On Tue, Oct 23, 2012 at 5:05 AM, Thouis (Ray) Jones wrote:
> On Fri, Oct 19, 2012 at 9:34 PM, Thouis (Ray) Jones wrote:
>> On Fri, Oct 19, 2012 at 4:46 PM, Thouis (Ray) Jones wrote:
>>> On Fri, Oct 19, 2012 at 11:20 AM, Thouis (Ray) Jones
>>> wrote:
I started the import with the oldest 75
On Fri, Oct 19, 2012 at 9:34 PM, Thouis (Ray) Jones wrote:
> On Fri, Oct 19, 2012 at 4:46 PM, Thouis (Ray) Jones wrote:
>> On Fri, Oct 19, 2012 at 11:20 AM, Thouis (Ray) Jones
>> wrote:
>>> I started the import with the oldest 75 and newest 125 Trac issues,
>>> and will wait a few hours to do t
On Fri, Oct 19, 2012 at 8:56 AM, Travis Oliphant wrote:
> Kudos! Ray.
>
> Very impressive and useful work.
Indeed, many thanks, Ray!! This has been a ton of work, and somewhat
thankless b/c it's for a one-off thing. What I did for our lanunchpad
bug migration was a far more hackish/dirty job pre
Also, it looks like Trac issues 2228 and up weren't in the snapshot of
the DB I had. Those should be imported after Trac is disabled for new
bugs.
Ray
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/nu
On Fri, Oct 19, 2012 at 4:46 PM, Thouis (Ray) Jones wrote:
> On Fri, Oct 19, 2012 at 11:20 AM, Thouis (Ray) Jones wrote:
>> I started the import with the oldest 75 and newest 125 Trac issues,
>> and will wait a few hours to do the rest to allow feedback, just in
>> case something is broken that I
On Fri, Oct 19, 2012 at 11:20 AM, Thouis (Ray) Jones wrote:
> I started the import with the oldest 75 and newest 125 Trac issues,
> and will wait a few hours to do the rest to allow feedback, just in
> case something is broken that I haven't noticed.
>
> I did make one change to better emulate Tra
Kudos! Ray.
Very impressive and useful work.
-Travis
On Oct 19, 2012, at 10:20 AM, Thouis (Ray) Jones wrote:
> I started the import with the oldest 75 and newest 125 Trac issues,
> and will wait a few hours to do the rest to allow feedback, just in
> case something is broken that I haven't noti
I started the import with the oldest 75 and newest 125 Trac issues,
and will wait a few hours to do the rest to allow feedback, just in
case something is broken that I haven't noticed.
I did make one change to better emulate Trac behavior. Some Trac
usernames are also email addresses, which Trac
On Wed, Oct 17, 2012 at 4:44 PM, Ralf Gommers wrote:
>
>
> On Tue, Oct 16, 2012 at 11:54 PM, Nathaniel Smith wrote:
>>
>> On Tue, Oct 16, 2012 at 9:06 PM, Thouis (Ray) Jones
>> wrote:
>> > On Sun, Oct 7, 2012 at 10:15 AM, Thouis (Ray) Jones
>> > wrote:
>> >> I plan to import all the Trac issues
On Tue, Oct 16, 2012 at 11:54 PM, Nathaniel Smith wrote:
> On Tue, Oct 16, 2012 at 9:06 PM, Thouis (Ray) Jones
> wrote:
> > On Sun, Oct 7, 2012 at 10:15 AM, Thouis (Ray) Jones
> wrote:
> >> I plan to import all the Trac issues to github by the end of this
> >> week. I want to get an up-to-date
On Tue, Oct 16, 2012 at 5:54 PM, Nathaniel Smith wrote:
> On Tue, Oct 16, 2012 at 9:06 PM, Thouis (Ray) Jones wrote:
>> On Sun, Oct 7, 2012 at 10:15 AM, Thouis (Ray) Jones wrote:
>>> I plan to import all the Trac issues to github by the end of this
>>> week. I want to get an up-to-date snapshot
On Tue, Oct 16, 2012 at 9:06 PM, Thouis (Ray) Jones wrote:
> On Sun, Oct 7, 2012 at 10:15 AM, Thouis (Ray) Jones wrote:
>> I plan to import all the Trac issues to github by the end of this
>> week. I want to get an up-to-date snapshot of the Trac DB, and run
>> another test import with it (just
On Sun, Oct 7, 2012 at 10:15 AM, Thouis (Ray) Jones wrote:
> I plan to import all the Trac issues to github by the end of this
> week. I want to get an up-to-date snapshot of the Trac DB, and run
> another test import with it (just to make sure there's nothing in
> recent bugs that isn't handled)
I plan to import all the Trac issues to github by the end of this
week. I want to get an up-to-date snapshot of the Trac DB, and run
another test import with it (just to make sure there's nothing in
recent bugs that isn't handled).
Previous test imports here:
https://github.com/thouis/numpy-trac-
On Fri, Sep 28, 2012 at 1:48 AM, Ralf Gommers wrote:
> Looks great! After a quick browse, the only thing I noticed that still needs
> some thought is the color scheme for the labels.
That's easy to adjust afterwards.
___
NumPy-Discussion mailing list
Nu
On Fri, Sep 28, 2012 at 4:20 AM, Thouis (Ray) Jones wrote:
> On Thu, Sep 27, 2012 at 10:09 PM, Thouis (Ray) Jones
> wrote:
> > tl;dr I think I fixed everything mentioned below.
>
> By the way, my current method is to address bugs in the import by just
> reimporting tickets that demonstrate the bu
On Thu, Sep 27, 2012 at 10:09 PM, Thouis (Ray) Jones wrote:
> tl;dr I think I fixed everything mentioned below.
By the way, my current method is to address bugs in the import by just
reimporting tickets that demonstrate the bug, and not worrying about
old versions of that ticket. If in browsing
tl;dr I think I fixed everything mentioned below.
On Thu, Sep 27, 2012 at 7:10 PM, Nathaniel Smith wrote:
> On Thu, Sep 27, 2012 at 3:22 PM, Thouis (Ray) Jones wrote:
>> On Thu, Sep 27, 2012 at 8:46 AM, David Cournapeau wrote:
>>
>>> Thouis, what needs to be done to make a testbed of the conver
On Thu, Sep 27, 2012 at 3:22 PM, Thouis (Ray) Jones wrote:
> On Thu, Sep 27, 2012 at 8:46 AM, David Cournapeau wrote:
>
>> Thouis, what needs to be done to make a testbed of the conversion ?
>
> I just returned to this a couple of days ago [*], and last night
> successfully imported all the trac
On Thu, Sep 27, 2012 at 9:58 AM, Thouis (Ray) Jones wrote:
> On Thu, Sep 27, 2012 at 11:46 AM, Charles R Harris
> wrote:
> >
> >
> > On Thu, Sep 27, 2012 at 8:22 AM, Thouis (Ray) Jones
> > wrote:
> >>
> >> On Thu, Sep 27, 2012 at 8:46 AM, David Cournapeau
> >> wrote:
> >>
> >> > Thouis, what ne
27.09.2012 21:45, Pauli Virtanen kirjoitti:
> 27.09.2012 15:46, David Cournapeau kirjoitti:
> [clip]
>> Ok, so scipy.org was down again because of trac. Unfortunately, the
>> machine on which scipy.org lives is the same as trac, and is a bit
>> messy.
>
> Trac runs on new.scipy.org, which AFAIK *
27.09.2012 15:46, David Cournapeau kirjoitti:
[clip]
> Ok, so scipy.org was down again because of trac. Unfortunately, the
> machine on which scipy.org lives is the same as trac, and is a bit
> messy.
Trac runs on new.scipy.org, which AFAIK *is* a different machine from
scipy.org.
Pauli
On Thu, Sep 27, 2012 at 11:46 AM, Charles R Harris
wrote:
>
>
> On Thu, Sep 27, 2012 at 8:22 AM, Thouis (Ray) Jones
> wrote:
>>
>> On Thu, Sep 27, 2012 at 8:46 AM, David Cournapeau
>> wrote:
>>
>> > Thouis, what needs to be done to make a testbed of the conversion ?
>>
>> I just returned to this
On Thu, Sep 27, 2012 at 8:22 AM, Thouis (Ray) Jones wrote:
> On Thu, Sep 27, 2012 at 8:46 AM, David Cournapeau
> wrote:
>
> > Thouis, what needs to be done to make a testbed of the conversion ?
>
> I just returned to this a couple of days ago [*], and last night
> successfully imported all the tr
On Thu, Sep 27, 2012 at 8:46 AM, David Cournapeau wrote:
> Thouis, what needs to be done to make a testbed of the conversion ?
I just returned to this a couple of days ago [*], and last night
successfully imported all the trac issues (from my somewhat
out-of-date snapshot) to this repo:
https://
On Sun, Jun 24, 2012 at 12:31 PM, Ralf Gommers
wrote:
>
>
> On Sat, Jun 23, 2012 at 11:30 AM, Thouis (Ray) Jones
> wrote:
>>
>> On Sat, Jun 23, 2012 at 11:13 AM, Ralf Gommers
>> wrote:
>> >
>> >
>> > On Sat, Jun 23, 2012 at 11:03 AM, Thouis (Ray) Jones
>> > wrote:
>> >>
>> >> On Fri, Jun 22, 20
On Sat, Jun 23, 2012 at 11:30 AM, Thouis (Ray) Jones wrote:
> On Sat, Jun 23, 2012 at 11:13 AM, Ralf Gommers
> wrote:
> >
> >
> > On Sat, Jun 23, 2012 at 11:03 AM, Thouis (Ray) Jones
> > wrote:
> >>
> >> On Fri, Jun 22, 2012 at 7:29 PM, Ralf Gommers
> >> wrote:
> >> >
> >> >
> >> > On Fri, Jun
On Sat, Jun 23, 2012 at 11:13 AM, Ralf Gommers
wrote:
>
>
> On Sat, Jun 23, 2012 at 11:03 AM, Thouis (Ray) Jones
> wrote:
>>
>> On Fri, Jun 22, 2012 at 7:29 PM, Ralf Gommers
>> wrote:
>> >
>> >
>> > On Fri, Jun 22, 2012 at 9:49 AM, Thouis (Ray) Jones
>> > wrote:
>> >>
>> >> On Mon, Jun 4, 2012
On Sat, Jun 23, 2012 at 11:03 AM, Thouis (Ray) Jones wrote:
> On Fri, Jun 22, 2012 at 7:29 PM, Ralf Gommers
> wrote:
> >
> >
> > On Fri, Jun 22, 2012 at 9:49 AM, Thouis (Ray) Jones
> > wrote:
> >>
> >> On Mon, Jun 4, 2012 at 7:43 PM, Travis Oliphant
> >> wrote:
> >> > I have turned on issue tra
On Fri, Jun 22, 2012 at 7:29 PM, Ralf Gommers
wrote:
>
>
> On Fri, Jun 22, 2012 at 9:49 AM, Thouis (Ray) Jones
> wrote:
>>
>> On Mon, Jun 4, 2012 at 7:43 PM, Travis Oliphant
>> wrote:
>> > I have turned on issue tracking and started a few labels. Feel free to
>> > add
>> > more / adjust the na
On Fri, Jun 22, 2012 at 9:49 AM, Thouis (Ray) Jones wrote:
> On Mon, Jun 4, 2012 at 7:43 PM, Travis Oliphant
> wrote:
> > I have turned on issue tracking and started a few labels. Feel free to
> add
> > more / adjust the names as appropriate. I am trying to find someone
> who
> > can help m
On Mon, Jun 4, 2012 at 7:43 PM, Travis Oliphant wrote:
> I have turned on issue tracking and started a few labels. Feel free to add
> more / adjust the names as appropriate. I am trying to find someone who
> can help manage the migration from Trac.
Are the github issues set up sufficiently
There is an interesting project called http://huboard.com/The projects
suggests using a few Column Labels that provides a nice card-based window onto
the Github issues.
I have turned on issue tracking and started a few labels. Feel free to add
more / adjust the names as appropriate.
On Mon, Jun 4, 2012 at 6:05 PM, Charles R Harris
wrote:
>
>
> On Mon, Jun 4, 2012 at 9:34 AM, Ralf Gommers
> wrote:
>
>>
>>
>> On Sun, Jun 3, 2012 at 10:06 PM, Charles R Harris <
>> charlesr.har...@gmail.com> wrote:
>>
>>> Hi All,
>>>
>>> The issue tracking discussion seems to have died. Since gi
On Mon, Jun 4, 2012 at 9:34 AM, Ralf Gommers wrote:
>
>
> On Sun, Jun 3, 2012 at 10:06 PM, Charles R Harris <
> charlesr.har...@gmail.com> wrote:
>
>> Hi All,
>>
>> The issue tracking discussion seems to have died. Since github issues
>> looks to be a viable alternative at this point, I propose to
On Sun, Jun 3, 2012 at 10:06 PM, Charles R Harris wrote:
> Hi All,
>
> The issue tracking discussion seems to have died. Since github issues
> looks to be a viable alternative at this point, I propose to turn it on for
> the numpy repository and start directing people in that direction.
>
> Thoug
Hi All,
The issue tracking discussion seems to have died. Since github issues looks
to be a viable alternative at this point, I propose to turn it on for the
numpy repository and start directing people in that direction.
Thoughts?
Chuck
___
NumPy-Discu
+1 on migrating issues to GitHub, I'm so glad this discussion is happening.
On Sat, May 5, 2012 at 8:28 PM, Charles R Harris
wrote:
> Uh oh. We are short on developers as is... Which brings up a question, do
> people need a github account to open an issue?
Creating an account on GH is currently
On Saturday, May 5, 2012, Charles R Harris wrote:
>
>
> On Sat, May 5, 2012 at 8:50 PM, Benjamin Root
>
> > wrote:
>
>>
>>
>> On Saturday, May 5, 2012, Pauli Virtanen wrote:
>>
>>> 05.05.2012 22:53, Ralf Gommers kirjoitti:
>>> [clip]
>>> > would be great to get it done by end of June.To
On Sat, May 5, 2012 at 8:50 PM, Benjamin Root wrote:
>
>
> On Saturday, May 5, 2012, Pauli Virtanen wrote:
>
>> 05.05.2012 22:53, Ralf Gommers kirjoitti:
>> [clip]
>> > would be great to get it done by end of June.To Charles' list
>> > and Ralf's suggestions, I would add setting up a
On Saturday, May 5, 2012, Pauli Virtanen wrote:
> 05.05.2012 22:53, Ralf Gommers kirjoitti:
> [clip]
> > would be great to get it done by end of June.To Charles' list
> > and Ralf's suggestions, I would add setting up a server that can
> > relay pull requests to the mailing list.
>
05.05.2012 22:53, Ralf Gommers kirjoitti:
[clip]
> would be great to get it done by end of June.To Charles' list
> and Ralf's suggestions, I would add setting up a server that can
> relay pull requests to the mailing list.
>
> Don't know if you saw this, but it looks like Pauli is
On Sat, May 5, 2012 at 10:19 PM, Travis Oliphant wrote:
>
> On May 5, 2012, at 2:28 PM, Ralf Gommers wrote:
>
>
>
> On Wed, May 2, 2012 at 11:25 PM, Wes McKinney wrote:
>
>> On Wed, May 2, 2012 at 9:48 AM, Charles R Harris
>> wrote:
>> >
>> >
>> > On Tue, May 1, 2012 at 11:47 PM, Ralf Gommers <
On May 5, 2012, at 2:28 PM, Ralf Gommers wrote:
>
>
> On Wed, May 2, 2012 at 11:25 PM, Wes McKinney wrote:
> On Wed, May 2, 2012 at 9:48 AM, Charles R Harris
> wrote:
> >
> >
> > On Tue, May 1, 2012 at 11:47 PM, Ralf Gommers
> > wrote:
> >>
> >>
> >>
> >> On Wed, May 2, 2012 at 1:48 AM, Paul
On Sat, May 5, 2012 at 1:28 PM, Ralf Gommers wrote:
>
>
> On Wed, May 2, 2012 at 11:25 PM, Wes McKinney wrote:
>
>> On Wed, May 2, 2012 at 9:48 AM, Charles R Harris
>> wrote:
>> >
>> >
>> > On Tue, May 1, 2012 at 11:47 PM, Ralf Gommers <
>> ralf.gomm...@googlemail.com>
>> > wrote:
>> >>
>> >>
>>
On Wed, May 2, 2012 at 11:25 PM, Wes McKinney wrote:
> On Wed, May 2, 2012 at 9:48 AM, Charles R Harris
> wrote:
> >
> >
> > On Tue, May 1, 2012 at 11:47 PM, Ralf Gommers <
> ralf.gomm...@googlemail.com>
> > wrote:
> >>
> >>
> >>
> >> On Wed, May 2, 2012 at 1:48 AM, Pauli Virtanen wrote:
> >>>
On Wed, May 2, 2012 at 9:48 AM, Charles R Harris
wrote:
>
>
> On Tue, May 1, 2012 at 11:47 PM, Ralf Gommers
> wrote:
>>
>>
>>
>> On Wed, May 2, 2012 at 1:48 AM, Pauli Virtanen wrote:
>>>
>>> 01.05.2012 21:34, Ralf Gommers kirjoitti:
>>> [clip]
>>> > At this point it's probably good to look again
On Tue, May 1, 2012 at 11:47 PM, Ralf Gommers
wrote:
>
>
> On Wed, May 2, 2012 at 1:48 AM, Pauli Virtanen wrote:
>
>> 01.05.2012 21:34, Ralf Gommers kirjoitti:
>> [clip]
>> > At this point it's probably good to look again at the problems we want
>> > to solve:
>> > 1. responsive user interface (m
On Wed, May 2, 2012 at 1:48 AM, Pauli Virtanen wrote:
> 01.05.2012 21:34, Ralf Gommers kirjoitti:
> [clip]
> > At this point it's probably good to look again at the problems we want
> > to solve:
> > 1. responsive user interface (must absolutely have)
>
> Now that it comes too late: with some luc
On 5/1/12 7:24 PM, Charles R Harris wrote:
> I would agree that a good search facility is essential, and not
> keyword/tag based. I've found some trac tickets with google on occasion,
> although not by initial intent.
I use google to search the sage trac these days, using a shortcut to
limit sear
On Tue, May 1, 2012 at 6:04 PM, wrote:
> maybe searching issues and pull requests is ok.
> The problem is that in statsmodels we did a lot of commits without
> pull requests, and I'm not very good searching in git either.
> (I don't remember which change I looked for but I got lost for half an
>
On Tue, May 1, 2012 at 8:29 PM, Fernando Perez wrote:
> On Tue, May 1, 2012 at 5:24 PM, Charles R Harris
> wrote:
>> I would agree that a good search facility is essential, and not keyword/tag
>> based.
>
> Github issues does have full-text search, and up until now I haven't
> really had too many
On Tue, May 1, 2012 at 5:24 PM, Charles R Harris
wrote:
> I would agree that a good search facility is essential, and not keyword/tag
> based.
Github issues does have full-text search, and up until now I haven't
really had too many problems with it. No sophisticated filtering or
anything, but ba
On Tue, May 1, 2012 at 6:18 PM, wrote:
> On Tue, May 1, 2012 at 7:48 PM, Pauli Virtanen wrote:
> > 01.05.2012 21:34, Ralf Gommers kirjoitti:
> > [clip]
> >> At this point it's probably good to look again at the problems we want
> >> to solve:
> >> 1. responsive user interface (must absolutely ha
On Tue, May 1, 2012 at 7:48 PM, Pauli Virtanen wrote:
> 01.05.2012 21:34, Ralf Gommers kirjoitti:
> [clip]
>> At this point it's probably good to look again at the problems we want
>> to solve:
>> 1. responsive user interface (must absolutely have)
>
> Now that it comes too late: with some luck, I
01.05.2012 21:34, Ralf Gommers kirjoitti:
[clip]
> At this point it's probably good to look again at the problems we want
> to solve:
> 1. responsive user interface (must absolutely have)
Now that it comes too late: with some luck, I've possibly hit on what
was ailing the Tracs (max_diff_bytes con
01.05.2012 21:34, Ralf Gommers kirjoitti:
[clip]
> The main problem with Github (besides the issues/PRs thing and no
> attachments, which I can live with) is that to make it work we'll have
> to religiously label everything. And because users aren't allowed to
> attach labels, it will require a lar
Thanks Ralf,
I agree that Pauli and David have a lot of say in what we do. Thanks for
reminding.We will wait to hear from them. If together you three feel like
we should set up a separate Redmine instance than we can do that and just pay
special attention with the Github integration an
On Tue, May 1, 2012 at 1:36 PM, Jason Grout wrote:
> This example indicates that basing your decision on what it is like
> *today* may not be valid either. You'd hope that they won't do
Very true ;)
> Anyway, like everyone else has said, Ralf, Pauli, et. al. are really the
> ones to vote in th
On 5/1/12 3:19 PM, Fernando Perez wrote:
> But if you do decide to go with GHI, it should be based on what the
> system is like*today*, not on the hope that it will get better.
> About a month ago they broke label filtering by turning multi-label
> filters into an OR operation, which effectively re
On Tue, May 1, 2012 at 2:17 PM, Charles R Harris
wrote:
>
>
> On Tue, May 1, 2012 at 1:34 PM, Ralf Gommers
> wrote:
>
>>
>>
>> On Tue, May 1, 2012 at 9:12 AM, Charles R Harris <
>> charlesr.har...@gmail.com> wrote:
>>
>>>
>>>
>>> On Tue, May 1, 2012 at 12:52 AM, Travis Oliphant wrote:
>>>
>>
Hi folks,
sorry for not jumping in before, swamped with deadlines...
On Mon, Apr 30, 2012 at 8:14 PM, Jason Grout
wrote:
> I've been pretty impressed with the lemonade that the IPython folks have
> made out of what I see as pretty limiting shortcomings of the github
> issue tracker. I've been
On Tue, May 1, 2012 at 1:34 PM, Ralf Gommers wrote:
>
>
> On Tue, May 1, 2012 at 9:12 AM, Charles R Harris <
> charlesr.har...@gmail.com> wrote:
>
>>
>>
>> On Tue, May 1, 2012 at 12:52 AM, Travis Oliphant wrote:
>>
>>>
>>> On Apr 30, 2012, at 10:14 PM, Jason Grout wrote:
>>>
>>> On 4/30/12 6:31 PM
On Tue, May 1, 2012 at 9:12 AM, Charles R Harris
wrote:
>
>
> On Tue, May 1, 2012 at 12:52 AM, Travis Oliphant wrote:
>
>>
>> On Apr 30, 2012, at 10:14 PM, Jason Grout wrote:
>>
>> On 4/30/12 6:31 PM, Travis Oliphant wrote:
>>
>> Hey all,
>>
>>
>> We have been doing some investigation of various a
01.05.2012 08:52, Travis Oliphant kirjoitti:
[clip]
>> 3. No attachments for issues (screenshots, supporting documents, etc.).
>> Having API access to data won't help you here.
>
> Using gists and references to gists can overcome this. Also using an
> attachment service like http://uploading.co
On 5/1/12 1:52 AM, Travis Oliphant wrote:
>> 1. No key:value pairs for labels (Fernando brought this up a long time
>> ago, I think). This is brilliant in Google code's tracker, and allows
>> for custom fields that help in tracking workflow (like status, priority,
>> etc.). Sure, you can do what t
On Tue, May 1, 2012 at 12:52 AM, Travis Oliphant wrote:
>
> On Apr 30, 2012, at 10:14 PM, Jason Grout wrote:
>
> On 4/30/12 6:31 PM, Travis Oliphant wrote:
>
> Hey all,
>
>
> We have been doing some investigation of various approaches to issue
> tracking. The last time the conversation left t
On Apr 30, 2012, at 10:14 PM, Jason Grout wrote:
> On 4/30/12 6:31 PM, Travis Oliphant wrote:
>> Hey all,
>>
>> We have been doing some investigation of various approaches to issue
>> tracking. The last time the conversation left this list was with Ralf's
>> current list of preferences as
On Tue, May 1, 2012 at 12:16 AM, Charles R Harris wrote:
>
>
> On Mon, Apr 30, 2012 at 10:14 PM, Travis Oliphant wrote:
>
>>
>>
>>> The same is true of SciPy.I think if SciPy also migrates to use
>>> Github issues, then together with IPython we can really be a voice that
>>> helps Github. I
On Mon, Apr 30, 2012 at 10:14 PM, Travis Oliphant wrote:
>
>
>> The same is true of SciPy.I think if SciPy also migrates to use
>> Github issues, then together with IPython we can really be a voice that
>> helps Github. I will propose to NumFOCUS that the Foundation sponsor
>> migration of t
>
> The same is true of SciPy.I think if SciPy also migrates to use Github
> issues, then together with IPython we can really be a voice that helps
> Github. I will propose to NumFOCUS that the Foundation sponsor migration of
> the Trac to Github for NumPy and SciPy.If anyone would l
On Mon, Apr 30, 2012 at 5:31 PM, Travis Oliphant wrote:
> Hey all,
>
> We have been doing some investigation of various approaches to issue
> tracking. The last time the conversation left this list was with
> Ralf's current list of preferences as:
>
> 1) Redmine
> 2) Trac
> 3) Github
>
> Sinc
On Monday, April 30, 2012, Travis Oliphant wrote:
> Hey all,
>
> We have been doing some investigation of various approaches to issue
> tracking. The last time the conversation left this list was with
> Ralf's current list of preferences as:
>
> 1) Redmine
> 2) Trac
> 3) Github
>
> Since that
On 4/30/12 6:31 PM, Travis Oliphant wrote:
> Hey all,
>
> We have been doing some investigation of various approaches to issue
> tracking. The last time the conversation left this list was with Ralf's
> current list of preferences as:
>
> 1) Redmine
> 2) Trac
> 3) Github
>
> Since that time,
Hey all,
We have been doing some investigation of various approaches to issue tracking.
The last time the conversation left this list was with Ralf's current list
of preferences as:
1) Redmine
2) Trac
3) Github
Since that time, Maggie who has been doing a lot of work settting up various
Jeroen's reply about the Sage "buildbot" is below:
>Jeroen, do we have an
> automatic buildbot system for Sage?
Depends on what you mean with "automatic". We have the buildbot setup
at http://build.sagemath.org/sage/waterfall which builds automatically
but I still have to change versions by ha
>I'm wondering about using one of these commercial issue tracking plans for
>NumPy and would like thoughts and comments.Both of these plans allow Open
>Source projects to have unlimited plans for free.
>
>JIRA:
>
>http://www.atlassian.com/software/jira/overview/tour/code-integration
>
>
On Mon, Feb 13, 2012 at 12:56 PM, Matthew Brett wrote:
> I have the impression that the Cython / SAGE team are happy with their
> Jenkins configuration.
So are we in IPython, thanks to Thomas Kluyver's recent leadership on
this front it's now running quite smoothly:
https://jenkins.shiningpanda.
Hi,
On Mon, Feb 13, 2012 at 2:33 PM, wrote:
> On 2/13/12 2:56 PM, Matthew Brett wrote:
>> I have the impression that the Cython / SAGE team are happy with their
>> Jenkins configuration.
>
> I'm not aware of a Jenkins buildbot system for Sage, though I think
> Cython uses such a system: https://
On 2/13/12 2:56 PM, Matthew Brett wrote:
> I have the impression that the Cython / SAGE team are happy with their
> Jenkins configuration.
I'm not aware of a Jenkins buildbot system for Sage, though I think
Cython uses such a system: https://sage.math.washington.edu:8091/hudson/
We do have a num
Hi,
On Mon, Feb 13, 2012 at 12:44 PM, Travis Oliphant wrote:
>
> On Mon, Feb 13, 2012 at 12:12 AM, Travis Oliphant
> wrote:
>>
>> I'm wondering about using one of these commercial issue tracking plans for
>> NumPy and would like thoughts and comments. Both of these plans allow
>> Open Source
>
> On Mon, Feb 13, 2012 at 12:12 AM, Travis Oliphant wrote:
> I'm wondering about using one of these commercial issue tracking plans for
> NumPy and would like thoughts and comments.Both of these plans allow Open
> Source projects to have unlimited plans for free.
>
> Free usage of a t
On Mon, Feb 13, 2012 at 12:12 AM, Travis Oliphant wrote:
> I'm wondering about using one of these commercial issue tracking plans for
> NumPy and would like thoughts and comments.Both of these plans allow
> Open Source projects to have unlimited plans for free.
>
> Free usage of a tool that's
I'm wondering about using one of these commercial issue tracking plans for
NumPy and would like thoughts and comments.Both of these plans allow Open
Source projects to have unlimited plans for free.
YouTrack from JetBrains:
http://www.jetbrains.com/youtrack/features/issue_tracking.html
88 matches
Mail list logo
