Am 2015-05-07 um 10:39 schrieb Jeroen Demeyer: > On 2015-05-06 21:24, Volker Braun wrote: >> There is no reason that "closed" should be final, until the new branch >> is published we *can* always back. That doesn't mean that you *should* >> dump a pile of extra bookkeeping on me. > > Let me make it clear that I don't want to dump a pile of extra bookkeeping on > you. Even if I think that the release manager's workflow is sub-optimal, I > will > still accept it and go along with the release manager. That's doesn't mean > that > I cannot disagree with it, especially if somebody asks for negative reactions.
I still have the impression that the situation is no clearer than before. I try to summarize the discussion so far: Current Workflow: if a ticket is set to positive_review and changed afterwards (including cycling the status through needs_work, needs_review, positive_review again) and if the earlier state is already processed by the release manager, then commits are lost. Proposed Solution 1: do not change any ticket which has been set to positive review and document this policy. Proposed Solution 2: Somehow introduce a flag that a positive_review ticket must no longer be changed because it is under consideration by the RM (many variants proposed, e.g. simply set it to "closed" or set some kind of flag in trac). Proposed Solution 3: check whether the commit had been changed during testing by the RM and take appropriate action then. Proposed Solution 4: somehow change the relation between trac tickets and commits entirely (I am not sure I understood that correctly). If I understood Volker correctly, he does not like Solution 3; he might consider Solution 2 with setting the ticket to "closed" when he starts merging. Proposed Solution 1 is seen by some as somehow restrictive. I emphasize that personally, I do not like the current situation which leads to losing commits but do not really care which of the solutions (or any other) is implemented. I simply think that there should be a solution, therefore I keep trying to prevent this thread from stalling and hope for some solution. Kind regards, Clemens -- 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.
