On 03/14/2015 03:13 PM, William Stein wrote: > On Sat, Mar 14, 2015 at 5:40 AM, Marc Mezzarobba <m...@mezzarobba.net> wrote: >> Hi, >> >> I don't know the release policy with respect to optional >> packages, but with 6.6.beta5: > > I don't think we have one. I wish we did, but it's a matter of > resources, and being release manager is already a huge amount of work.
I thought we used to have one, namely that RCs and of course final releases (but not alphas/betas) are supposed to work with *any* optional package, otherwise an optional package would simply become experimental again (in the worst case only of course); but I fail to find that policy in the old release management documentation [1] at least... ;-) It's not necessarily up to the release manager to include all optional packages in (late) release tests; IMHO an optional package's /maintainer/ should occasionally test whether it still works with current betas, and always make sure it does work with RCs. In case it doesn't, that's worth a blocker ticket, solved by either fixing the issue or -- as a last resort -- by removing it from the optional packages list as mentioned. W.r.t. the buildbots: Besides increased testing time, AFAIK not all optional packages can be tested at once, i.e. one would need a couple of (?) different sets of optional packages to be tested one after the other. -leif [1] http://wiki.sagemath.org/devel/ReleaseManagement > I definitely don't think anybody wants to make a release where > optional doctests fail. Currently, I don't think anybody > systematically runs the optional tests. I tried to at various points > over the years, on at least one system; however, it's a huge amount of > work to maintain. > > ** Anybody want to volunteer to maintain testing of each Sage beta > release and a well-defined subset of the optional packages and tests, > on at least one platform? ** > > -- William > >> >> $ ./sage -t --optional=sage,coxeter3 src/sage/libs/coxeter3/coxeter.pyx >> Running doctests with ID 2015-03-14-13-38-10-11823038. >> Git branch: develop >> Doctesting 1 file. >> sage -t --warn-long 73.0 src/sage/libs/coxeter3/coxeter.pyx >> ********************************************************************** >> File "src/sage/libs/coxeter3/coxeter.pyx", line 723, in >> sage.libs.coxeter3.coxeter.CoxGroupElement._coxnumber >> Failed example: >> w._coxnumber() >> # optional - coxeter3 >> Expected: >> 7L >> Got: >> 7 >> ********************************************************************** >> 1 item had failures: >> 1 of 5 in sage.libs.coxeter3.coxeter.CoxGroupElement._coxnumber >> [257 tests, 1 failure, 0.24 s] >> ---------------------------------------------------------------------- >> sage -t --warn-long 73.0 src/sage/libs/coxeter3/coxeter.pyx # 1 doctest >> failed >> ---------------------------------------------------------------------- >> Total time for all tests: 0.3 seconds >> cpu time: 0.2 seconds >> cumulative wall time: 0.2 seconds >> >> -- >> Marc >> >> -- >> 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 sage-release+unsubscr...@googlegroups.com. >> To post to this group, send email to sage-release@googlegroups.com. >> Visit this group at http://groups.google.com/group/sage-release. >> 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 sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at http://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.