On 2017-12-08 15:56, Erik Bray wrote:
Right now the way it (seems to) work is new tickets get assigned to the next release milestone. That release is then made...whenever...regardless of what tickets are still open or not, and then all those tickets (typically) remain in old milestones for completed releases. This is nobody's fault; it just doesn't seem to be part of the practice or culture of the project to really use milestones in a consistent manner.
What you are saying is totally true, but I just don't see it as a problem. Probably we should be more explicit about it and just stop using the "milestone" field on Trac.
However, I don't think that there is anything fundamentally wrong with "That release is then made...whenever...regardless of what tickets are still open or not". One exception is blocker tickets and the release manager does consider those: a blocker ticket will indeed block a release. But for non-blocker tickets, it doesn't really matter much in which release those tickets are merged.
-- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
