I'd say replacing this with a mild-mannered script that does the said "automatic ticket rejections" would be an improvement for the project. Key ingredients: - Respect the ticket milestone. - Post the build logs when it fails. If you need help implementing this script, let me know.
On Saturday, January 22, 2022 at 3:55:25 PM UTC-8 Volker Braun wrote: > No, I'm not running a private CI service for the Sage project. I'm relying > on you all to only positively review tickets that actually work. > > In the rare cases where somebody is inexperienced or there is some > unexpected interaction between tickets I typically lend a hand and provide > some hints on the ticket. But for those that should know better I'm not > doing that any more since I feel like that gives the wrong incentive (= > instead of testing it myself I'll just let Volker run the tests and then > report back any errors) > > On Saturday, January 22, 2022 at 7:55:03 PM UTC+1 [email protected] > wrote: > >> On Saturday, January 22, 2022 at 9:57:03 AM UTC-8 Volker Braun wrote: >> >>> I'm actively looking at ways to improve this, and the solution will be >>> [...] automatic ticket rejections >>> >> >> Wait... are you telling us that the process that is setting tickets back >> from "positive review" to "needs work" with 0 details is _not_ a script >> currently? >> > -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/8887e727-2934-4aa0-9ef5-77baabca49e7n%40googlegroups.com.
