> So what is really necessary is (good) documentation on how to do this
> quickly and efficiently since a few people have replied to this thread
> and claimed that it should only take 30 seconds to do this.
Yup. Or maybe even better, partially automatize the task as follow:
sage -combinat post mypatch-reviewed.patch
This would do sanity checks, run the hg export, and print on the
screen the remaining steps to be done by the developer. Something
like:
------------------------------------------------------------------------------
Patch /tmp/mypatch-reviewed exported.
Are you sure this patch has been properly reviewed? Doc tests? Design? ...?
If yes, please do the following steps to finish posting it on Sage trac:
- connect to: http://trac.sagemath.org/sage_trac/newticket
- create a new ticket with:
short summary: mypatch [with patch, positive review]
component: combinatorics
milestone: sage-combinat
CC: sage-combinat-commits
attached file: /tmp/mypatch-reviewed.patch
comment:
... output of hg log, url of patch, ...
- take note of the trac patch number, and run:
hg qrename mypatch-reviewed.patch mypatch-posted-<trac number>.patch
------------------------------------------------------------------------------
(in case the patch is named after -final.patch, then this would just
suggest to post it with [with patch, needs review]
After some experience with this, we can decide whether we want to
automatize part or all of the remaining step(s) or not.
Cheers,
Nicolas
--
Nicolas M. Thiéry "Isil" <[EMAIL PROTECTED]>
http://Nicolas.Thiery.name/
--~--~---------~--~----~------------~-------~--~----~
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-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
