On Wed, Jun 12, 2019 at 11:45 AM Dima Pasechnik <[email protected]> wrote: > > On Tue, Jun 11, 2019 at 7:52 AM E. Madison Bray <[email protected]> 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 the > > community. > > > my ongoing complaint is the lack of progress on the improving the > release procedures to make it easy to change the configure package. > At the moment it is extremely sub-optimal, with endless merge > conflicts resulting solely from the need to have the ticket branch > that changes configure.ac, spkg-configure.m4 files, and its friends, > such as sage/big/sage-env* things coming with its configure "package" > tarball. This leaves tickets of this sort languishing for months, as > it's not really possible to get them in sync with the ongoing release > process (already due to configure tarballs coming with artificial > version numbers, that should not clash etc). > > I continue to think that the release process should not require > updates of configure package. Sage seems to unique in its insistence > on the release process depending on the autogenerated dumps...
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. Yes, it's generated. But there's precedent for this. Among other projects, CPython includes their configure script in the repository. This allows developers to get right up-and-running with ./configure without having to fuss with the nuances of different versions of autotools on different systems. Only developers actually working on configure issues need to worry about that. It's quite convenient. > > On Tue, Jun 11, 2019, 02:28 Kwankyu Lee <[email protected]> wrote: > >> > >> > >> > >> On Monday, June 10, 2019 at 4:40:52 PM UTC+9, Sébastien Labbé wrote: > >>> > >>> Testing the following optional and external packages: > >>> > >>> External software detected for doctesting: > >>> ffmpeg,graphviz,gurobi,imagemagick,internet,latex,pandoc > >>> > >>> Using > >>> --optional=4ti2,bliss,cbc,ccache,cmake,cryptominisat,dot2tex,e_antic,external,glucose,latte_int,lidia,lrslib,memlimit,mpir,ninja_build,normaliz,notedown,openssl,pandoc_attributes,pycosat,pynormaliz,python2,qhull,rst2ipynb,sage,topcom > >>> External software to be detected: > >>> cplex,ffmpeg,graphviz,gurobi,imagemagick,internet,latex,macaulay2,magma,maple,mathematica,matlab,octave,pandoc,scilab > >>> > >>> I get: > >>> > >>> ---------------------------------------------------------------------- > >>> sage -t --long src/sage/databases/findstat.py # 8 doctests failed > >>> sage -t --long src/sage/combinat/designs/ext_rep.py # 1 doctest failed > >>> ---------------------------------------------------------------------- > >>> > >>> and only the following is reproducible: > >>> > >>> ---------------------------------------------------------------------- > >>> sage -t --long src/sage/databases/findstat.py # 8 doctests failed > >>> ---------------------------------------------------------------------- > >>> > >>> Follow up at https://trac.sagemath.org/ticket/25536 > >> > >> > >> I see Sage has been much improved in this respect. Thank you for your > >> persistent efforts! > >> > >> -- > >> You received this message because you are subscribed to the Google Groups > >> "sage-release" group. > >> To unsubscribe from this group and stop receiving emails from it, send an > >> email to [email protected]. > >> To post to this group, send email to [email protected]. > >> Visit this group at https://groups.google.com/group/sage-release. > >> To view this discussion on the web visit > >> https://groups.google.com/d/msgid/sage-release/35dc58d0-763e-4da4-b1c4-e8f981665b49%40googlegroups.com. > >> For more options, visit https://groups.google.com/d/optout. > > > > -- > > You received this message because you are subscribed to the Google Groups > > "sage-release" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [email protected]. > > To post to this group, send email to [email protected]. > > Visit this group at https://groups.google.com/group/sage-release. > > To view this discussion on the web visit > > https://groups.google.com/d/msgid/sage-release/CAOTD34bCgqGe6UCE2eoDVq%2Bmg%2BW8f3nnRrBKztutSLvT%2BjicdQ%40mail.gmail.com. > > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "sage-release" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/sage-release. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-release/CAAWYfq1bWWce%2B-tN7V%2B-E7DGAFOGvu3L7san5WDR-M6p%2B0bA2A%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-release. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/CAOTD34YrKuwSpzzdvcZHfbXM53zrZujSHa4kCDOaPpFxF9cJqQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
