On Sun, Apr 17, 2011 at 7:38 PM, Robert Miller <[email protected]> wrote: > I'm not sure exactly how the buildbot works, but it seems to be > automatically testing new patches against sage-4.6.2, even though the > latest (dev) sage is 4.7.alpha4.
Seems we've moved away from the "release early, release often" strategy and now alphas are essentially the new release (except they are allowed to have doctest failures, etc.) The fact that the latest release is not good enough to develop off of is unfortunate for both budding and veteran developers. But, I guess that's how things are now... On that note, should we be more prominently featuring these alpas on our page if this is what people should be using? > Isn't it a waste of (someone's) > computing resources to be using such an outdated version? Well, feel free to ignore the results and apply the patch/run the tests yourself :). Note that if a patch does not apply cleanly, very little compute time is lost. Actually, the intent was (still is) to merge this into Sage itself, and so anyone could run a buildbot against whatever Sage on whatever system they had (though it probably makes sense to just run one such bot on sage.math, which could be against the latest alpha if that was automated, or even better against the rolling hg tip of the release manager). We'll need to make it better at dependency checking and perhaps whitelisting known doctest failures. Anyways, building a 4.7 alpha now... - Robert -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
