On 4/18/11 2:54 PM, John Cremona wrote:
On Mon, Apr 18, 2011 at 11:38 AM, Volker Braun<[email protected]> wrote:
The buildbot tests patches on top of the latest release, not alpha/beta
versions. There was some discussion on sage-devel about this behavior.
Although annoying, it might not be such a bad idea to keep track of the
dependencies of your patch back to the latest official release.
I really disagree strongly with this. If I were writing a patch now I
would definitely base it on 4.7.alpha4, especially as it may well
depend critically on other things merged since 4.6.2. If the buildbot
cannot handle that, I'm not going to put myself out for a machine's
convenience.
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?
Thanks,
Jason
--
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
