[sage-devel] Re: spkg statistics

2013-07-06 Thread Volker Braun
And speaking of version bumps, there is a trivial IPython update that has been sitting on trac for two weeks: http://trac.sagemath.org/14810 -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails

Re: [sage-devel] Re: spkg statistics

2013-07-05 Thread Robert Bradshaw
Interesting stats. On Fri, Jul 5, 2013 at 8:13 AM, Volker Braun wrote: > I'd be happy if there were more frequent reviews of updated packages, for > example I packaged Gap-4.6.3 (http://trac.sagemath.org/14039) and it just > lingered on trac until 4.6.4 came out. IMHO we should just get rid of so

[sage-devel] Re: spkg statistics

2013-07-05 Thread Volker Braun
Sorry if I wasn't clear, the package maintainer must of course make sure that the doctests pass. Usually there are some minor changes, e.g. we do doctest the GAP version number which will always change. Or the output order of the upstream source changes. That does require some good judgement to

[sage-devel] Re: spkg statistics

2013-07-05 Thread Simon King
Hi Volker, On 2013-07-05, Volker Braun wrote: > I'd be happy if there were more frequent reviews of updated packages, for > example I packaged Gap-4.6.3 (http://trac.sagemath.org/14039) and it just > lingered on trac until 4.6.4 came out. IMHO we should just get rid of some > of the red tap fo

[sage-devel] Re: spkg statistics

2013-07-05 Thread Volker Braun
I'd be happy if there were more frequent reviews of updated packages, for example I packaged Gap-4.6.3 (http://trac.sagemath.org/14039) and it just lingered on trac until 4.6.4 came out. IMHO we should just get rid of some of the red tap for pure version bumps; If the package maintainer makes an