> > I agree--I think there should be at least one buildbot run > per-platform--maybe not for every issue but at least run once a week, > that tests building all optional packages and running tests that use > them (i.e. tagged with # optional - <packagename>). > > A build with broken optional packages could then be considered a broken > build. >
Or even starting at rc time. But if an optional package is broken on most platforms we provide builds for, then either there is something wrong with the package (-> experimental) or we changed API or there is a new bug in Sage (-> blocker). However, that does presuppose the "maintainer" model we talked about a number of years ago, where someone really does say they take responsibility for the optional package for (say) 3 years. I don't know if that has happened in practice. By the way, Simon has been remarkably patient w.r.t. his package, which has a lot of moving parts for complex computations. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
