#16030: Use "git trac" in the developer guide
-------------------------------------+-------------------------------------
Reporter: vbraun | Owner:
Type: enhancement | Status: needs_info
Priority: major | Milestone: sage-6.2
Component: documentation | Resolution:
Keywords: | Merged in:
Authors: Volker Braun | Reviewers: Ralf Stephan
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/vbraun/use__git_trac__in_the_developer_guide|
49ee6a57ca0520b8b279bc185b3410056dcdc747
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by vbraun):
I agree of course that the bar of entry should be as low as possible. One
thing that I could do is start with just "readonly" access where you get
the sources and make changes. And then have a separate section talk about
uploading those changes. What do you think about that?
About my roadmap, I've been developing the git trac script over the last 6
months and they form the core of my release management workflow. I've
implemented pretty much everything that I think should go in there, so now
its time to start steering people towards using them. This is part of the
reason for being very frank about `sage -dev`, I don't want to dis anybody
but I want to steer any newcomer in the right (or what I think is right
;-) direction.
--
Ticket URL: <http://trac.sagemath.org/ticket/16030#comment:12>
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.
