Hello Volker, > I'm happy to switch to closed when I merge it, and not only when it tests > ok.
Works for me. This way we will know the last commit that you consider in your script, and we run no danger of adding a new one after that. > Eventually the > merge will be done by a script, so ideally tickets will only stay for > seconds in the positive_review state then. Essentially, we'll get rid of > positive_review state and any opportunity to make changes. Well, when the merging process will be "continuous and live" the problem will indeed be solved by itself, while currently there can be days or weeks before a ticket gets merged, and very often we do have time to add a commit safely. > Which ends up > being the same as just agreeing not to make changes to positive_review > tickets right now. Err. Well, it *will* the same as agreeing to not make changes to positive_review tickets <when the tickets will be tested&merged right after we set them to positive_review>. And I don't think that any of us disagrees with that. Thanks, Nathann -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
