#13015: Metaticket: revamp workflow / switch to git
-------------------------------------------------------------------------+--
Reporter: kini |
Owner: jason
Type: task |
Status: new
Priority: major |
Milestone: sage-6.0
Component: misc |
Resolution:
Keywords: git workflow |
Work issues:
Report Upstream: N/A |
Reviewers:
Authors: |
Merged in:
Dependencies: #9906, #11080, #13031, #13032, #13123, #13432, #13448 |
Stopgaps:
-------------------------------------------------------------------------+--
Description changed by rohana:
Old description:
> We plan to revamp the development workflow for Sage, involving a few
> separate (big) changes:
>
> - switch to git (switch to using commits and a history graph for
> collaboration rather than patch files)
> - consolidate our repositories into a single repository
> - simplified development interface
> - etc. (many other ideas)
>
> Help develop scripts and other things related to this project at
> http://github.com/kini/sage-workflow . We are not making subtickets
> because this is such a big change that it won't really make sense to get
> most of this stuff into Sage until after the switchover to git and a
> single repo, and also because collaboration is faster this way.
>
> Related tickets:
>
> * #13025 and its subtickets, to clean up some SPKGs
> * #13190 and #13201, switch sage library to setuptools and allow for
> parallel easy_installs
>
> This ticket description needs to be expanded...
New description:
We plan to revamp the development workflow for Sage, involving a few
separate (big) changes:
* switch to git
* switch to using commits and a history graph for collaboration rather
than patch files
* consolidate our repositories into a single repository
* main 4 repos for now, spkgs can be merged in one by one after we
transition
* simplified development interface
* etc.
Help develop scripts and other things related to this project at
http://github.com/kini/sage-workflow . A significant portion of the work
to transition to git can be done before we actually carry it out (without
affecting how sage presently functions). For these portions, we are making
tickets and adding them as dependencies.
Related tickets:
* #13025 and its subtickets, to clean up some SPKGs
* #13190 and #13201, switch sage library to setuptools and allow for
parallel easy_installs
This ticket description needs to be expanded...
--
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13015#comment:13>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
