On Tue, Jun 28, 2016 at 10:20 PM, Volker Braun wrote:
> On Tuesday, June 28, 2016 at 6:23:18 PM UTC+2, Erik Bray wrote:
>>
>> Currently the release manager *closes* a ticket and marks it as
>> "fixed" when merging the change for testing.
>
>
> No. Tickets are closed *after* tests succeed.
I'm jus
On Tuesday, June 28, 2016 at 6:23:18 PM UTC+2, Erik Bray wrote:
>
> Currently the release manager *closes* a ticket and marks it as
> "fixed" when merging the change for testing.
No. Tickets are closed *after* tests succeed.
The only race condition is if somebody else reopens positively review
On Tue, Jun 28, 2016 at 4:06 PM, Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
> On 28/06/16 16:04, Erik Bray wrote:
>>
>> Hi all,
>>
>> The current ticket workflow in Trac only allows creating new tickets
>> with a status 'new'. So when posting a branch with proposed changes,
>> for exampl
Hi all,
The current ticket workflow in Trac only allows creating new tickets
with a status 'new'. So when posting a branch with proposed changes,
for example it is necessary to create the ticket, and then immediately
update it to needs_review.
This is fine for tickets that don't immediately have
On 28/06/16 16:04, Erik Bray wrote:
Hi all,
The current ticket workflow in Trac only allows creating new tickets
with a status 'new'. So when posting a branch with proposed changes,
for example it is necessary to create the ticket, and then immediately
update it to needs_review.
This is fine f
Hello,
I'd like to make some tweaks to the workflow on Sage's trac server, in
particular the annoying fact that you can't go from needs_work to
positive_review (in the case that someone forgets to update the status
when they post in reply to a reviewer). I'm pretty sure I have the
right permission
