Clemens Heuberger wrote: > Am 2015-05-07 um 03:42 schrieb leif: >> I might be wrong, but isn't it trivial to check whether the branch of a >> ticket changed (after you merged it into some preliminary release)? > > It is easy to check. But what if it did change? This might lead to an infinite > cycle, as outlined before.
Well, this simply should not happen [by accident], or will happen very rarely, provided the authors and reviewers are aware it is currently subject to testing/inclusion. If the branch got updated, or simply the ticket's status changed (to needs review or needs work), the ticket gets dropped from the list of tickets for inclusion until it has positive review again. Almost the same as what happens when the *release manager* decides to not include / unmerge the ticket, e.g. because of build or doctest errors. The only difference being that *someone else* came to the conclusion it isn't yet ready to get merged. -leif -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
