On Dec 28, 2007 3:54 AM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
>
> Are there some instructions for Sage package maintainers to follow?
> I.e. what exact steps are neede to update the package?
There are no instructions, and no master list of package maintainers, etc.
One of the goals of this thread is to create such things.
> 1) create a new spkg
> 2) create a trac ticket and attach it? or expose the repository, so
> that you can build it yourself?
> 3) write to the mailinglist?
We need:
(a) a wiki page that lists packages with the corresponding maintainer.
(b) A natural system for updating patches. I like your suggestion above,
though _not_ the order.
(1) Create a trac ticket describing that the package is out of date.
This should _already_ be done for every package I listed at
the beginning of this email.
(2) Accept the trac ticket when you're about to make a new spkg.
(3) Post a link from the trac ticket to the new spkg (don't
attach it, since
it is too big.)
(4) Post to sage-devel announcing the new spkg and requesting
feedback and testing. Any such email *must* list some tests
a user can try after "sage -i" 'ing the package to test that
it actually installed OK. All feedback from such testing
should be pasted into the trac ticket. The trac ticket should
be assigned against an upcoming release of Sage.
(5) The release manager puts the new spkg in Sage once it
has got a positive review as a part of (4).
Thoughts?
-- William
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
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://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---
