Differences between revisions 12 and 13
Revision 12 as of 2013-03-30 20:36:00
Size: 3823
Editor: swenson
Comment: Added comment about swenson's work on github
Revision 13 as of 2013-04-02 01:23:07
Size: 4097
Editor: nthiery
Comment:
Deletions are marked like this. Additions are marked like this.
Line 18: Line 18:
  * Sage combinat queue
    * Entire queue imported into git
    * separate branches with dependencies
  * Sage combinat queue and mercurial queues import
    * Prototypical tool to automatically import a Mercurial queue into GIT.
    * Each patch/ticket is imported in its own branch, with
      dependencies handling (from appropriate annotations in the
      series file)
    * Most of the Sage-Combinat queue can imported into git
Line 75: Line 78:
   * Motivate the choice of GIT as DVCS.

Accomplishments

  • Programmatically add, edit tickets on trac
    • New trac installation
    • XML-RPC interface, doctests (authenticated and anonymous)
  • Gitolite server
    • web portals both through trac and gitweb
    • programatic authenticated and anonymous access
    • auto ssh-keys upload
  • Build system
    • Works on linux, OS X 10.6
      • givaro/gcc issues on 10.7+
    • Lots of work on portage system
      • also running into OS X errors
  • Sage combinat queue and mercurial queues import
    • Prototypical tool to automatically import a Mercurial queue into GIT.
    • Each patch/ticket is imported in its own branch, with
      • dependencies handling (from appropriate annotations in the series file)
    • Most of the Sage-Combinat queue can imported into git
  • Sage Dev Scripts
  • Patchbot
    • Pull patches from git branches on trac.
    • Update build, plugins, etc. to accommodate new directory structure (work in progress)
  • Other

Migration Plan

  • Sage-5.9 will be last export to git
    • Simultaneous git/classic sdist, bdist
  • Sage-5.10[.betaX] merged/cherry picked/rebased atop stable Sage git repo
    • Tickets worked on in git will be (auto) exported to patches on trac
    • Last classic release
  • Sage-6.0
    • Tickets worked on in hg will be imported into git
    • Release done from git master

Still to be done

Necessary now

  • Make the git version build on all of Sage's supported platforms
  • Finish writing, debugging and documenting the basic features in the development scripts. Command-line version.
  • Write functions in development scripts for exporting a patch to the old model.
  • Add features to our trac plugin (dependency-aware diff)
  • Write documentation of the workflow for a Sage developer: one for people who know Sage's current workflow.
  • Write something to sage-devel about the plan
  • Git version of patchbot
  • Motivate the choice of GIT as DVCS.

Necessary before 6.0

  • Write hooks for gitolite and development scripts (whitespace, abandonment, pushing changes to trac, prohibit committing to master)
  • Switch to trac-info in repo model
  • Write doctests so that the development scripts can be included into the Sage library.
  • Add features to our trac plugin (updates to certain ticket fields are pushed to the branch)
  • Write documentation of the workflow for a Sage developer: one for newbies, one for people who are familiar with git.
  • Release process scripts

Desirable

  • Write additional features for development scripts

sagedaysgit/status (last edited 2013-04-04 01:46:53 by roed)