> Could you please point me to documentation about the new tracker? I want
> to study the best way to extract information from it (right now, I'm
> just pulling htmls from SF and parsing them, and that's not easy, fast,
> nor clean).
The tracker software is roundup. It's documentation is at
http:
Martin v. Löwis wrote:
> When you do, make sure you take a look at roundup's search facilities.
> Roundup keeps a 'last activity' field, on which you can search and sort,
> and a 'creation date' field (likewise).
Could you please point me to documentation about the new tracker? I want
to study th
"| On 3/20/07, Facundo Batista <[EMAIL PROTECTED]> wrote:
| > Brett Cannon wrote:
| > > old and had not been touched in ages. Hopefully you will be able to
| > > easily port this over to the new tracker once it's up (that should
| > > happen 2-4 weeks after 2.5.1 is released).
| >
| > You can be
>> old and had not been touched in ages. Hopefully you will be able to
>> easily port this over to the new tracker once it's up (that should
>> happen 2-4 weeks after 2.5.1 is released).
>
> You can be sure I'll port it...
When you do, make sure you take a look at roundup's search facilities.
Ro
On 3/20/07, Facundo Batista <[EMAIL PROTECTED]> wrote:
> Brett Cannon wrote:
>
> > That's some interesting stuff. Took me a second to realize that the
> > temporal column's total length is the time range from the opening of
> > the oldest bug to the latest comment made on any bug and that the blue
Brett Cannon wrote:
> That's some interesting stuff. Took me a second to realize that the
> temporal column's total length is the time range from the opening of
> the oldest bug to the latest comment made on any bug and that the blue
> bar is where within that time frame the bug was opened and th
On 3/20/07, Facundo Batista <[EMAIL PROTECTED]> wrote:
> People:
>
> At the beginning of March, there was a thread in this list about patchs
> and bugs that teorically weren't checked out.
>
> >From that discussion, I asked myself: "How can I know the temporal
> location of a patch/bug?". Are there
People:
At the beginning of March, there was a thread in this list about patchs
and bugs that teorically weren't checked out.
>From that discussion, I asked myself: "How can I know the temporal
location of a patch/bug?". Are there a lot of old patchs/bugs? Those
that are old, don't have any updat
