#18228: Developer guide: Do not change tickets with status "positive_review"
-------------------------------------+-------------------------------------
Reporter: cheuberg | Owner:
Type: defect | Status: needs_review
Priority: major | Milestone: sage-6.7
Component: documentation | Resolution:
Keywords: | Merged in:
Authors: Clemens Heuberger | Reviewers:
Report Upstream: N/A | Work issues:
Branch: u/cheuberg/doc | Commit:
/do-not-change-positive-review- | e18c88688732d8d26ff3fc4a0723d14e8a37cf16
tickets | Stopgaps:
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by cheuberg):
Replying to [comment:12 ncohen]:
> Yet another alternative mentionned by Volker: a two-weeks period between
a merge and the latest commit. I know that Thierry would be interested by
something like that.
I never understood that proposal: a two-weeks cooling down period might
reduce the probability of another push to a ticket, but does not make them
impossible.
For those who rely on the diff view of trac, a two weeks interval would
mean that reviewing chains of dependent tickets would take months.
--
Ticket URL: <http://trac.sagemath.org/ticket/18228#comment:14>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" 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-trac.
For more options, visit https://groups.google.com/d/optout.
