#15527: Automatically pick up version for bdist
-------------------------------------+-------------------------------------
Reporter: vbraun | Owner:
Type: enhancement | Status: closed
Priority: major | Milestone: sage-6.0
Component: scripts | Resolution: fixed
Keywords: | Merged in:
Authors: Volker Braun | Reviewers: R. Andrew Ohana
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/vbraun/bdist_version | 7673476bbfdf8522b86eaed8551a2206cdbfac28
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by kcrisman):
I don't follow. Even if a branch has several tickets it ends up closing,
each individual commit should surely be connected (if only morally) to a
given ticket? If a ticket is closed as not valid because a later one
subsumes it, that is fine - the later one is the ticket. If this isn't
possible in the new workflow, at the very least one could go back to the
(quite successful, at the time) policy of asking everyone to put the
ticket # in the commit message. This seems very reasonable and we already
did it.
And now `git trac` becomes almost necessary, which is sort of unfortunate.
{{{
$ git log | grep 15527
Trac #15527: Automatically pick up version for bdist
URL: http://trac.sagemath.org/15527
commit 0c2032f1bbf24a1552715ea3bbefd646def0a902
$ git log 0c2032f
commit 0c2032f1bbf24a1552715ea3bbefd646def0a902
Merge: fd93366 8a0a800
Author: William Stein <[email protected]>
Date: Mon Aug 27 13:24:26 2007 -0700
merge
}}}
This is even more confusing. In fact, it's commit 15d89e9.
I get that there is this nonlinear structure. But that means the ticket
#s are more important, not less, because `git log` is pretty useless for
trying to figure order out (bisecting) and it would be nice not to have to
be a git expert to find out what caused a problem.
Anyway, you also shouldn't have to be a git expert - or to have to guess
about `git trac find` since
[http://sagemath.org/doc/developer/git_trac.html#chapter-git-trac the
developer guide section on git trac doesn't have it] - in order to guess
the ticket.
Nor to guess the version of Sage a given 'ticket' is merged in! Since
Jeroen automated these things, I can't see why it is so horrible to try
them again... but I suppose I don't have much chance of prevailing here.
--
Ticket URL: <http://trac.sagemath.org/ticket/15527#comment:7>
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.
