Re: [sage-release] Re: Sage 8.8.rc0 released

2019-06-12 Thread Dima Pasechnik
On Tue, Jun 11, 2019 at 7:52 AM E. Madison Bray wrote: > > I don't know why the rush to call this a release candidate when there are > clearly still several outstanding problems to be resolved before the next > release. > > As usual absolutely zero communication of a plan or coordination with th

Re: [sage-release] Re: Sage 8.8.rc0 released

2019-06-12 Thread E. Madison Bray
On Wed, Jun 12, 2019 at 11:45 AM Dima Pasechnik wrote: > > On Tue, Jun 11, 2019 at 7:52 AM E. Madison Bray wrote: > > > > I don't know why the rush to call this a release candidate when there are > > clearly still several outstanding problems to be resolved before the next > > release. > > > >

Re: [sage-release] Re: Sage 8.8.rc0 released

2019-06-12 Thread Dima Pasechnik
On Wed, Jun 12, 2019 at 1:05 PM E. Madison Bray wrote: > > On Wed, Jun 12, 2019 at 11:45 AM Dima Pasechnik wrote: > > > > On Tue, Jun 11, 2019 at 7:52 AM E. Madison Bray > > wrote: > > > > > > I don't know why the rush to call this a release candidate when there are > > > clearly still several

Re: [sage-release] Re: Sage 8.8.rc0 released

2019-06-12 Thread Dima Pasechnik
On Wed, Jun 12, 2019 at 1:46 PM Dima Pasechnik wrote: > > On Wed, Jun 12, 2019 at 1:05 PM E. Madison Bray wrote: > > > > On Wed, Jun 12, 2019 at 11:45 AM Dima Pasechnik wrote: > > > > > > On Tue, Jun 11, 2019 at 7:52 AM E. Madison Bray > > > wrote: > > > > > > > > I don't know why the rush to

Re: [sage-release] Re: Sage 8.8.rc0 released

2019-06-12 Thread E. Madison Bray
On Wed, Jun 12, 2019 at 2:46 PM Dima Pasechnik wrote: > > On Wed, Jun 12, 2019 at 1:05 PM E. Madison Bray wrote: > > > > On Wed, Jun 12, 2019 at 11:45 AM Dima Pasechnik wrote: > > > > > > On Tue, Jun 11, 2019 at 7:52 AM E. Madison Bray > > > wrote: > > > > > > > > I don't know why the rush to

Re: [sage-release] Re: Sage 8.8.rc0 released

2019-06-12 Thread Dima Pasechnik
On Wed, Jun 12, 2019 at 2:03 PM E. Madison Bray wrote: > > On Wed, Jun 12, 2019 at 2:46 PM Dima Pasechnik wrote: > > > > On Wed, Jun 12, 2019 at 1:05 PM E. Madison Bray > > wrote: > > > > > > On Wed, Jun 12, 2019 at 11:45 AM Dima Pasechnik wrote: > > > > > > > > On Tue, Jun 11, 2019 at 7:52 AM

Re: [sage-release] Re: Sage 8.8.rc0 released

2019-06-12 Thread E. Madison Bray
On Wed, Jun 12, 2019 at 3:14 PM Dima Pasechnik wrote: > > On Wed, Jun 12, 2019 at 2:03 PM E. Madison Bray wrote: > > > > On Wed, Jun 12, 2019 at 2:46 PM Dima Pasechnik wrote: > > > > > > On Wed, Jun 12, 2019 at 1:05 PM E. Madison Bray > > > wrote: > > > > > > > > On Wed, Jun 12, 2019 at 11:45

Re: [sage-release] Re: Sage 8.8.rc0 released

2019-06-12 Thread Dima Pasechnik
On Wed, Jun 12, 2019 at 2:42 PM E. Madison Bray wrote: > > On Wed, Jun 12, 2019 at 3:14 PM Dima Pasechnik wrote: > > > > On Wed, Jun 12, 2019 at 2:03 PM E. Madison Bray > > wrote: > > > > > > On Wed, Jun 12, 2019 at 2:46 PM Dima Pasechnik wrote: > > > > > > > > On Wed, Jun 12, 2019 at 1:05 PM

[sage-release] Re: Sage 8.8.rc0 released

2019-06-12 Thread Eric Gourgoulhon
On Ubuntu 18.04 running on bi-Xeon E5-2623 (8 cores) + 16 GB RAM: *- python2: * - build (-j16) from a fresh git clone + pull develop completed, with Sphinx complaining during the doc build: formatargspec() is now deprecated. Please use sphinx.util.inspect.Signature instead - all tes

Re: [sage-release] Re: Sage 8.8.rc0 released

2019-06-12 Thread Volker Braun
On Wednesday, June 12, 2019 at 2:05:04 PM UTC+2, E. Madison Bray wrote: > > One very easily solution to this, and I know some people will shudder > (myself included) is to simply include the configure script in the > repository. We already have a way of bundling up the configure scripts in a ta

Re: [sage-release] Re: Sage 8.8.rc0 released

2019-06-12 Thread Dima Pasechnik
On Wed, Jun 12, 2019 at 6:13 PM Volker Braun wrote: > > On Wednesday, June 12, 2019 at 2:05:04 PM UTC+2, E. Madison Bray wrote: >> >> One very easily solution to this, and I know some people will shudder >> (myself included) is to simply include the configure script in the >> repository. > > > We