On 9/1/07, mabshoff <[EMAIL PROTECTED]> wrote: > > > > In that case, what is the right way to "notify" that a patch has been > > attached? I guess what I'm saying is: how does the main repository > > maintainer know where to look for tickets that are probably ready to > > be closed? Is that managed by the "milestone" field? Is there some > > database query that picks these things up? > > No, No and No. The only chance to catch an attached patch is to look > at it manually (bad, but we are getting better at it) or being in the > CC field. I think that we should create a sage-trac-ticket google > group and just CC any chances there per default. It is high traffic, > but for the few of us who want to watch the flow of tickets it migh > make things easier to deal with. > > Coming into #sage-devel and announcing that a patch has been created > might be the best short term solution. >
Actually, I think the best solution is to do all the above plus attach the trac ticket to a milestone. Basically, when we want to release that milestone, we desperately want to close all the tickets attached to that milestone, and to do that we look at the tickets and any attached patches very closely to see if they really do the job. > > I want to avoid a > > situation where people attach patches which sit on trac for months > > without being looked at. If those patches are attached to an upcoming milestone, they will *definitely* get looked at. If they aren't, though probably only will if Michael notices them when doing triage. > Hopefully we go those applied & closed during the last two weeks. I > went through all the tickets and tagged everything with a patch as > 2.8.x, so at least the older ones should all be gone. I check > periodically (mostly when I am bored/not motivated to do any "real" > work) and Mike Hansen has also been seen checking tickers, so with at > least 2 people paying attention it shouldn't be too bad. Bu having a > resolved status would really be nice to pretty much focus attention on > those issues. > William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
