On Mon, Sep 13, 2010 at 3:37 AM, David Kirkby <david.kir...@onetel.net> wrote: >>> True. But if person A creates the ticket, person B reviews it and the >>> release manager finds it passes, it may end up getting merged. >> >> I see that as someone not doing there job properly if we were to decide that >> a vote is required in that case. Let's face it, we can always imagine a >> scenario where safeguards fails. We are just minimizing risks and damages. >> >> Francois > > But the current rules permit this. > > * Person A decides to update a .spkg to a non-stable release > * There's no need to discuss it on sage-devel or have a vote. > * Person B reviews this unstable release and gives it positive review. > * The release manager merges this snapshot and we all suffer. > > This is the current situation, and one I feel is very wrong. My thread > has only attracted responses from yourself and Jason, so perhaps it's > not of interest to many.
If we have to send everything to a vote, this will paralyze development. Both person A and person B and the manager should be aware that a given spkg is off an unstable release, and feel comfortable with the justifications for using it rather than the old version. - Robert -- 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
