On 2 Sep, 05:55, François Bissey <f.r.bis...@massey.ac.nz> wrote:
> > Who would agree with making this a policy and so adding to the Sage > > Developers Guide a few sentences saying that any updates of packages > > that are not to a stable release (i.e snapshots, alpha, beta, release > > candidates etc) should be discussed on sage-devel first? > > > +1 or -1 ? > > +1 > > but how do you make it more visible? I do not understand what you mean. Do you mean visible in the Sage Developers Guide? Since I think it's quite important, putting part of it in bold might be a good idea. Or do you mean more visible on sage-devel? Perhaps a subject line of "Can we upgrade $package to a non-stable release?" might be a good idea. > Do you want to have a vote as well? I'd not really considered that. I guess a vote would be a good idea, though I think the main thing is that it is discussed > There was a very short thread about numpy-1.5 before the dev opened the > ticket and started coding. > Of course a ticket opened with code in it doesn't mean that it can be blindly > merged so there could be a second gate at this point before a decision is > made to merge. > Francois 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. -- 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
