Diff for "sagedaysgit/status"

Differences between revisions 10 and 11

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
- Entire queue imported into git
- separate branches with dependencies
Sage Dev Scripts
- Public interface design
- Fleshed out docstrings, some testing
- Preliminary implementation, integration with external trac/git services.
- https://github.com/sagemath/sage-workflow
Patchbot
- Pull patches from git branches on trac.
- Update build, plugins, etc. to accommodate new directory structure (work in progress)
Other
- New doctesting framework
- Tweak export scripts
- Bugfixes and ticket reviews in anticipation of git switch
  - #13031
  - #14384
  - #6415
  - #3355
  - #14379
  - #14377
  - #14226
  - #14376
  - #14369
  - #14331
  - #14385
  - #14316
  - #14383
  - #14328
  - ...

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

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

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

-  ⇤ ← Revision 10 as of 2013-03-30 02:01:31 → 
  Size: 2488
  Editor: rohana
  Comment:
+   ← Revision 11 as of 2013-03-30 03:48:41 → ⇥
  Size: 3703
  Editor: roed
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 62:
+== 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

=== 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