On 2017-07-02 08:03, Kwankyu Lee wrote:
1. Add a new ticket status "needs_feedback". This is a status between "new" and "needs_review".
I would guess that the problems are not technical, so technical solutions won't help. Maybe sage-feature branches don't get merged because they are too optimistic, too much work, adding a feature that nobody cares about...
2. Let patchbots test sage-feature tickets in needs_feedback status.
I don't see the point of early testing on the patchbot. Usually, when working on a ticket (a "normal" ticket or a "feature" ticket), there are just a few files relevant to that ticket. You can easily test those yourself.
The patchbot is meant to test other unrelated parts of Sage and to test the patch on different systems. But that's something that you would normally only do when the ticket is mostly finished. And even if you really want the patchbot to test a branch for some reason, you could still set the ticket to needs_review with a comment that it's just for the patchbot.
Currently patchbots refuse to test tickets in sage-feature milestone.
If so, that's a bug which should be fixed. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
