On Tue, Jun 28, 2016 at 7:14 PM, leif <not.rea...@online.de> 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/ ;-)
Yes, but I didn't want to imply "fault" here or anything like that. Volker does what's best for Volker and that's completely fine. The problem is that there aren't any documented procedures (that I know of!) for how testing of issues, merging, and releases should be handled. So the correct procedure *is* whatever the current release manager does. That, I do have a problem with, though it's nobody's fault. >> "fixed" when merging the change for testing. This really makes no >> sense--if the tests fail the issue is not "fixed". After >> "positive_review" can we add a "in testing" status or the like (from >> which the next stages can be either back to "needs_work" or >> "resolved". > > We had at least one lengthy discussion regarding that in the past (last > time probably a year ago? -- too lazy to search the thread[s] now, but > they're certainly worth reading [again]). > > Nothing happened since then though, if I'm not mistaken. > > But note that the buildbots do test tickets having positive review, some > also those with "needs review", so with relatively frequent "beta > releases", it's not all that bad. I'm really confused about what the buildbots do or don't do. Or what the relationship is between patchbot and buildbot (other than the latter implying that someone is managing a bunch of buildbot instances somewhere?) -- 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.
