Hello all,
I know this has been discussed before, but I only read the thread after
the fact and don't quite understand the problems.
I think that (as before in Mercurial-land) it should be possible to
review a given ticket without its dependencies. It should be possible to
see what code a ticket has contributed without seeing the contributions
of its dependencies.
I think this could easily be done as follows. Consider a ticket T and
the following merges:
(A) the merge of "master" with T's dependencies
(B) the merge of (A) with T.
In case any of these produces a merge conflict, then that fact should
simply be indicated (like the "does not merge cleanly" we have now).
Then the diff that I like to see is the diff from (A) to (B).
Essentially, that shows how the diff would look like, assuming that the
ticket dependencies have been merged. Ideally, the diff would remain
there even after the ticket has been merged (that's another disadvantage
of the new workflow, we cannot see any useful diffs after the ticket has
been merged).
Then adds a very slight burden on the release manager to not merge any
ticket unless the dependencies have been merged. But that was never a
big deal for me.
I have no idea how difficult it would be to actually implement this, but
in principle, this should work, right? Or why not?
Jeroen.
--
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/groups/opt_out.
