On 2012-03-06 15:17, Georg S. Weber wrote: > Thirdly (and most importantly), we could change to a "multispeed" > approach, i.e. new Sage releases (all the x.y versions, say, and some > x.y.z with, say, even z) are tested and verified mainly only on the > main few architecture/systems (the current version and one version > earlier of Ubuntu, Fedora/Redhat, OS X, and only x86_64 each), with > binary releases only for those too (!), including the Sage Virtual > image; followed by (say) Sage releases x.y.1 resp. x.y.'z+1', which > are then stabilized for the broad variety of the rest of the supported > architectures and systems. Building myself OS X 10.4 versions for > years now, I know that people don't complain "too loud" about > sometimes getting "their" binary release later (or that sometimes an > entire version is leapfrogged), as long as there is a constant flow of > updates (although the frequency might be lower). I can see this potentially working within *beta* releases (i.e. x.y.z.betaA for odd A) but not between releases. It would be just too complicated.
-- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
