On Sat, Mar 3, 2012 at 12:15 PM, Michael Orlitzky wrote:
> On 03/02/2012 02:29 PM, kcrisman wrote:
>>
>>
>> IF the patchbot actually applied the right patches to the right
>> development version, naturally, which I suppose is what you mean in
>> the next line?
>>
>
> I meant that it would suck if
On 03/02/2012 02:29 PM, kcrisman wrote:
IF the patchbot actually applied the right patches to the right
development version, naturally, which I suppose is what you mean in
the next line?
I meant that it would suck if the patchbot marked a ticket "needs work"
because e.g. it ran out of memory
On 03/02/12 03:07, Robert Bradshaw wrote:
> On Tue, Feb 28, 2012 at 5:48 PM, Michael Orlitzky
> wrote:
>> On 02/28/2012 07:33 PM, Keshav Kini wrote:
>>>
>>>
>>> It's not much consolation right now, but this will become easier once we
>>> switch to git, as branches can be automatically checked for
On Wed, Feb 29, 2012 at 5:47 AM, Jason Grout
wrote:
> On 2/28/12 11:19 PM, kcrisman wrote:
>>
>> "Needs reviewer", or
>> something - that's probably not the right wording, but you get the
>> point.
>
>
> Exactly what I was going to suggest, if we are indeed going to go in the
> direction of yet an
On Thu, Mar 1, 2012 at 1:38 AM, P Purkayastha wrote:
>
>
> On Thursday, March 1, 2012 5:25:32 PM UTC+8, John Cremona wrote:
>>
>> On 29 February 2012 22:23, David Roe wrote:
>> > You can use the custom query:
>> >
>> > http://trac.sagemath.org/sage_trac/query?status=needs_review&author=~cremona&o
On Tue, Feb 28, 2012 at 5:48 PM, Michael Orlitzky wrote:
> On 02/28/2012 07:33 PM, Keshav Kini wrote:
>>
>>
>> It's not much consolation right now, but this will become easier once we
>> switch to git, as branches can be automatically checked for whether they
>> are still mergeable into trunk or n
On Thursday, March 1, 2012 5:25:32 PM UTC+8, John Cremona wrote:
>
> On 29 February 2012 22:23, David Roe wrote:
> > You can use the custom query:
> >
> http://trac.sagemath.org/sage_trac/query?status=needs_review&author=~cremona&order=priority&col=id&col=summary&col=status&col=type&col=priorit
On 29 February 2012 22:23, David Roe wrote:
> You can use the custom query:
> http://trac.sagemath.org/sage_trac/query?status=needs_review&author=~cremona&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component
>
Thanks for that hint, but I find the results
You can use the custom query:
http://trac.sagemath.org/sage_trac/query?status=needs_review&author=~cremona&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component
On Wed, Feb 29, 2012 at 14:10, John Cremona wrote:
> OK, I am happy with using the CC field in
OK, I am happy with using the CC field in this way, though I would
still want to be able to CC someone without the implication that I was
suggesting them as a reviewer. If I really want to ask someone to
review my work, though, I would prefer to ask them directly (say by
email) as has happened to
> > ticket but don't want to review it, or remove yourself from the CC list.
>
> By the way, I don't think this removes one from Trac notification
> emails for that ticket, correct?
>
I don't know. I think it should if you've never commented on the ticket.
David
--
To post to this group, send an
I think the problem William is trying to resolve is that there are lots of
tickets marked as "need review" on trac, where nobody besides the author
feels any responsibility for getting them reviewed. Perhaps the idea of
using the CC field for this purpose is a good one: whenever you mark a
ticket
I agree with Rob. I think it is completely unacceptable to list a
person as a reviewer unless they have previously volunteered, or
responded to an explicit request (which they might decline). The
analogy with refereeing papers for publication is apt.
John
On 29 February 2012 17:16, Rob Beezer
On Tue, Feb 28, 2012 at 7:49 PM, kcrisman wrote:
> Some reasons for +1, in addition to Michael's (and I don't think that
> a git switch would help much with his reasons, unless everyone had
> access to the release manager's brain):
> * What about a first-time contributor to Sage of brand-new code
On 02/28/2012 07:33 PM, Keshav Kini wrote:
It's not much consolation right now, but this will become easier once we
switch to git, as branches can be automatically checked for whether they
are still mergeable into trunk or not. Well, the same could be done with
patches I guess but it would requi
15 matches
Mail list logo
