[sage-devel] Re: 404 on Sage Developer Conventions

2013-12-26 Thread kcrisman
On Thursday, December 26, 2013 7:38:22 AM UTC-5, Maarten Derickx wrote: > > It is now at: http://www.sagemath.org/doc/developer/coding_basics.html > > The name of the url changed, but if you look at the index > http://www.sagemath.org/doc/developer/index.html you can still easily > find it. > >

Re: [sage-devel] "git trac" command

2013-12-26 Thread R. Andrew Ohana
On Wed, Dec 25, 2013 at 12:36 PM, Volker Braun wrote: I've been working on a "git trac" subcommand to complement the git suite > with trac integration instead of the separate UI that the sage -dev scripts > present. This project is the basis for my release management scripts, so I > have been eati

[sage-devel] Re: Remaining Mercurial patches

2013-12-26 Thread Keshav Kini
maldun writes: > And I have another question: why github? afaik bitbucket would allow > to use both git and mercurial. So it is possible for users to submit > a mercurial patch on a git repo and vice versa. I think this would > avoid a lot of compability issues. I've never heard of such a featur

Re: [sage-devel] Reviewing package version updates (in particular, gap)

2013-12-26 Thread Robert Bradshaw
Reviewing spkgs used to be really painful--you had to unpack the new spkg and the old one and compare them manually, make sure the repo was up-to-date, the src/ was unmodified upstream, SPKG.txt had a (redundant) changelog entry, look at the patch files, etc. Also, rebuilding Sage to test a package

[sage-devel] Re: Broken link on sagemath.org for new spkg layout

2013-12-26 Thread Harald Schilly
Thank's that's fixed. I've only seen it now since I cannot read all emails. Hence, in the future CC me or just email me directly about such small bugs. Harald On Monday, December 23, 2013 9:02:58 PM UTC+1, Jean-Pierre Flori wrote: > > It seems that http://www.sagemath.org/upstream lacks packages

Re: [sage-devel] Reviewing package version updates (in particular, gap)

2013-12-26 Thread Travis Scrimshaw
You can do a custom query (http://trac.sagemath.org/query but you can find it under the "View tickets" tab) with the status being needs_review and the component as "packages: standard". Best, Travis On Wednesday, December 25, 2013 3:38:12 PM UTC-8, François wrote: > > Yes it is. But it is no

[sage-devel] Re: Reviewing package version updates (in particular, gap)

2013-12-26 Thread Volker Braun
That reminds me of one thing that I wanted to mention... I'm of course assuming that the package comes from either the maintainer (see SPKG.txt) or somebody whom I trust to have the technical abilities. In any case I'll always have a quick look... On Thursday, December 26, 2013 4:39:56 AM UTC

Re: [sage-devel] building sage 6.0 on debian live (squeeze)

2013-12-26 Thread Emil Widmann
Am Mittwoch, 25. Dezember 2013 20:40:41 UTC schrieb Thierry (sage-googlesucks@xxx): > > Hi, > > On Mon, Dec 23, 2013 at 02:07:12PM -0800, Emil Widmann wrote: > > I am trying to build the latest sage release with the possible goal of > > releasing another Live image version (USB/CD/HD disk ima

[sage-devel] Re: Reviewing package version updates (in particular, gap)

2013-12-26 Thread Nathann Cohen
> > How about a slight twist on the first option: > > [X] Have a whitelist of developers who are allowed to post an updated > package and set them to positive review immediately (listing themselves as > reviewers) because they judge the update to be trivial and in no need of > discussion > > It

[sage-devel] Re: 404 on Sage Developer Conventions

2013-12-26 Thread Maarten Derickx
It is now at: http://www.sagemath.org/doc/developer/coding_basics.html The name of the url changed, but if you look at the index http://www.sagemath.org/doc/developer/index.html you can still easily find it. Le mercredi 25 décembre 2013 16:32:22 UTC+1, Darij Grinberg a écrit : > > Hi guys, > >