Erik Bray wrote:
> On Fri, Jul 1, 2016 at 8:11 PM, leif wrote:
>> Jori Mäntysalo wrote:
>>> On Fri, 1 Jul 2016, Erik Bray wrote:
>>>
One thing that will help, which has already been discussed up-thread,
is having Trac help take care of the little nitty-gritty checks on
tickets.
>>>
On Fri, Jul 1, 2016 at 8:11 PM, leif wrote:
> Jori Mäntysalo wrote:
>> On Fri, 1 Jul 2016, Erik Bray wrote:
>>
>>> One thing that will help, which has already been discussed up-thread,
>>> is having Trac help take care of the little nitty-gritty checks on
>>> tickets.
>>
>> True. It feels extremel
No I haven't. Really it should be a trac plugin that prevents you from
setting a ticket to positive review without filling out Author and Reviewer
fields.
A somewhat orthogonal issue is whether to record plain text names or user
ids. The advantage of plain text is that anyone can be listed (),
>
>
> I think Jeroen *did* automate the posts regarding empty author and/or
> reviewer fields when he was release manager. :-)
>
I'm pretty sure that Volker automates this too...
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe
On Fri, 1 Jul 2016, leif wrote:
True. It feels extremely stupid to get a message "You forgot reviewer's
name.", as this is exactly what computers should do instead of humans.
You cannot automatically add these names; all we could do is create some
plug-in such that when a ticket is set to "pos
Jori Mäntysalo wrote:
> On Fri, 1 Jul 2016, Erik Bray wrote:
>
>> One thing that will help, which has already been discussed up-thread,
>> is having Trac help take care of the little nitty-gritty checks on
>> tickets.
>
> True. It feels extremely stupid to get a message "You forgot reviewer's
> n
On Fri, 1 Jul 2016, Erik Bray wrote:
One thing that will help, which has already been discussed up-thread,
is having Trac help take care of the little nitty-gritty checks on
tickets.
True. It feels extremely stupid to get a message "You forgot reviewer's
name.", as this is exactly what comput
On Thu, Jun 30, 2016 at 11:58 PM, William Stein wrote:
> On Thu, Jun 30, 2016 at 8:35 AM, Erik Bray wrote:
>> On Tue, Jun 28, 2016 at 7:14 PM, leif wrote:
>>> Erik Bray wrote:
While we're tinkering with the workflow, I think we need to change the
workflow associated with testing change
On Thu, Jun 30, 2016 at 8:35 AM, Erik Bray wrote:
> On Tue, Jun 28, 2016 at 7:14 PM, leif wrote:
>> Erik Bray wrote:
>>> While we're tinkering with the workflow, I think we need to change the
>>> workflow associated with testing changes.
>>>
>>> Currently the release manager *closes* a ticket and
Erik Bray wrote:
> On Tue, Jun 28, 2016 at 7:14 PM, leif wrote:
>> Erik Bray wrote:
>>> While we're tinkering with the workflow, I think we need to change the
>>> workflow associated with testing changes.
>>>
>>> Currently the release manager *closes* a ticket and marks it as
>>
>> s/currently the
On Tue, Jun 28, 2016 at 7:14 PM, leif wrote:
> Erik Bray wrote:
>> While we're tinkering with the workflow, I think we need to change the
>> workflow associated with testing changes.
>>
>> Currently the release manager *closes* a ticket and marks it as
>
> s/currently the release manager/the curre
leif wrote:
> Erik Bray wrote:
>> While we're tinkering with the workflow, I think we need to change the
>> workflow associated with testing changes.
>>
>> Currently the release manager *closes* a ticket and marks it as
>
> s/currently the release manager/the current release manager/ ;-)
>
>> "fi
Erik Bray wrote:
> While we're tinkering with the workflow, I think we need to change the
> workflow associated with testing changes.
>
> Currently the release manager *closes* a ticket and marks it as
s/currently the release manager/the current release manager/ ;-)
> "fixed" when merging the ch
13 matches
Mail list logo
