On 20 Okt., 19:10, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote: > So my concrete proposal would be: any author of a needs_review ticket > can ask the release manager to merge his ticket in the next alpha > release, the release manager then decides which needs_review tickets to > merge. If the ticket does not get a positive_review by the time the > release candidate comes out, it gets removed again. > > As a side effect of this, it might also be easier to find reviewers for > these tickets, because they can test it simply by downloading the latest > alpha.
We should just make sure tickets don't get a positive review (and finally merged) *solely* by "blind" testing, i.e., the *code* / sources should also still get properly reviewed by at least one person. But I agree it seems often the case a mature ticket doesn't get a positive review early (and therefore not merged) just because the reviewer hesitates due to a lack of resources (accessible test platforms or simply time to test on a wider range of systems). Also, in case an already merged "needs review" ticket requires further changes, it should be well-documented on the ticket which patch(es) went into which alpha. An alternative for larger tickets is of course to open follow-ups. If not too many tickets get tested this way, there shouldn't be much trouble with rebasing other tickets that were based on a later unmerged "volatile" one. 2ct, -Leif -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
