I think Russell put it very well in pointing out that one of the few
big technological impediments in Trac is that there isn't an easy way
to see the last-modification time of tickets. Particularly to the
point that it's hard to tell when a new patch is uploaded and an
accepted ticket might need ne
On Tue, Oct 5, 2010 at 9:58 AM, Tai Lee wrote:
> Hi Russ,
>
> On Oct 5, 11:48 am, Russell Keith-Magee
> wrote:
>
>> > Perhaps we need another triage stage for these tickets, "Needs final
>> > review" or something?
>>
>> That's essentially what RFC is. This is an area where our documented
>> proce
Hi Russ,
On Oct 5, 11:48 am, Russell Keith-Magee
wrote:
> There have been a couple of suggestions recently that the contributing
> guide should be distilled into a specific HOWTO for new users. I
> suppose the idea here would be for the contribution guide to be the
> letter of the law, and the H
On Tue, Oct 5, 2010 at 8:16 AM, Tai Lee wrote:
> Hi Jacob,
>
> Thanks for your feedback.
>
>> For (1) check out http://code.djangoproject.com/wiki/Reports(it's
>> linked in the nav). If there's anything missing there, please feel
>> free to add it -- it's a wiki page. Let me know if you need help
Hi Jacob,
Thanks for your feedback.
> For (1) check out http://code.djangoproject.com/wiki/Reports(it's
> linked in the nav). If there's anything missing there, please feel
> free to add it -- it's a wiki page. Let me know if you need help
> figuring out the linked query syntax.
I wasn't able to
On Fri, Oct 1, 2010 at 1:44 AM, Tai Lee wrote:
> I'd like to suggest (1) easy to find and use pre-defined searches to
> find tickets at each stage of triage, (2) a clearer indication of the
> next steps and the person responsible for it whenever a ticket is
> reviewed, and (3) tickets that have be
On Sep 30, 7:22 pm, Russell Keith-Magee
wrote:
> What is also needed is a whole lot more people volunteering. Any
> suggestions on how to get more people doing the entirely unglamorous,
> but completely necessary work will be gratefully accepted.
I'd like to suggest (1) easy to find and use pre-
On 09/30/2010 01:22 PM, Russell Keith-Magee wrote:
So, let me be clear on what you're proposing: you acknowledge that the
triage process is backlogged. Your proposal is to put extra workload
onto the core team - the one group that is already a bottleneck in the
process.
Pretty much. I just don'
On Thursday, September 30, 2010, Ivan Sagalaev
wrote:
> On 09/30/2010 03:46 AM, Russell Keith-Magee wrote:
>
> Accepted tickets can be:
>
> * Purely accepted, indicating that someone has verified that the
> problem exists, but not how to solve it
>
> * Accepted with a patch that is wrong in so
On 09/30/2010 03:46 AM, Russell Keith-Magee wrote:
Accepted tickets can be:
* Purely accepted, indicating that someone has verified that the
problem exists, but not how to solve it
* Accepted with a patch that is wrong in some way (e.g., fixing the
symptom, not the problem)
* Accepted wi
On Thu, Sep 30, 2010 at 9:14 AM, Waylan Limberg wrote:
> On Wed, Sep 29, 2010 at 7:46 PM, Russell Keith-Magee
> wrote:
>> On Thu, Sep 30, 2010 at 7:26 AM, Luke Plant wrote:
>>> On Thu, 2010-09-30 at 01:32 +0400, Ivan Sagalaev wrote:
>>>
My suggestion is about this unfortunate ticket status
On Wed, Sep 29, 2010 at 7:46 PM, Russell Keith-Magee
wrote:
> On Thu, Sep 30, 2010 at 7:26 AM, Luke Plant wrote:
>> On Thu, 2010-09-30 at 01:32 +0400, Ivan Sagalaev wrote:
>>
>>> My suggestion is about this unfortunate ticket status -- 'Accepted'.
>>> This now works as a sort of a dusty shelf: wh
On Thu, Sep 30, 2010 at 7:26 AM, Luke Plant wrote:
> On Thu, 2010-09-30 at 01:32 +0400, Ivan Sagalaev wrote:
>
>> My suggestion is about this unfortunate ticket status -- 'Accepted'.
>> This now works as a sort of a dusty shelf: when anyone of the core team
>> looks at the patch and decides that t
On Thu, 2010-09-30 at 01:32 +0400, Ivan Sagalaev wrote:
> My suggestion is about this unfortunate ticket status -- 'Accepted'.
> This now works as a sort of a dusty shelf: when anyone of the core team
> looks at the patch and decides that there's nothing wrong with it he
> puts it on that shelf
On 09/30/2010 01:40 AM, Chuck Harmston wrote:
In my world, the "accepted" status should only be used in one
circumstance: when a person is actively developing under or maintaining
a patch for the ticket. It's an indicator that someone has taken
ownership of a ticket, to prevent duplication of eff
In my world, the "accepted" status should only be used in one circumstance:
when a person is actively developing under or maintaining a patch for the
ticket. It's an indicator that someone has taken ownership of a ticket, to
prevent duplication of effort, etc. For example, I accepted ticket #25
dur
Hello Jacob and everyone.
On 09/29/2010 09:59 PM, Jacob Kaplan-Moss wrote:
Starting today, we're going to be making some minor but significant changes
to the way the Django core committer team "does business."
That's about time :-). Congratulations and thank you!
I have a comment and a sugges
Hi folks --
Starting today, we're going to be making some minor but significant changes
to the way the Django core committer team "does business."
Put simply, we're changing the way we make decisions so that we can make
important policy and design calls more quickly and easily. In a nutshell:
*
18 matches
Mail list logo
