Hello sage-devel, I would like to open a discussion on merging needs_review tickets in alpha versions of Sage. Since alpha versions are meant for testing, I think tickets can be tested earlier if they are merged in an alpha. I'm certainly not saying we should be doing this for all tickets, but in certain cases (especially for "big" tickets) it would help. For example, for the PARI upgrade #9343, I have made several "prealphas" for testing. I think these could have been "true" alphas. Another example is ticket #9896.
We have to be careful not to do this to too many tickets otherwise we lose track of what's happening, but for a few tickets each release I think it can be justified. 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. I'm completely open for your opinions on this matter. Jeroen. -- 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
