On 18 April 2011 21:18, Tom Boothby <[email protected]> wrote: > On Mon, Apr 18, 2011 at 1:11 PM, Jason Grout > <[email protected]> wrote: > >> Instead of keeping track of dependencies back to 4.6.2, for example, can we >> just list a dependency as "4.7.alpha4" and have the build-bot understand >> that as a meta-dependency and apply everything up to 4.7.alpha4? > > What if the alpha has test failures? Otherwise +1.
To my knowledge, all projects which use a buildbot do so against the latest sources, not the latest stable resources. It's clear there are advantages and disadvantages to both approaches. The vast majority of positively reviewed patches which are merged do not get backed out, so I think the advantages in basing tests on the very latest sources, rather than the latest stable sources, is best. It is certainly not a perfect solution, but I personally think given most merged patches stay merged, it is the best solution. Dave -- 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
