On Mar 6, 10:52 am, "Georg S. Weber" <georgswe...@googlemail.com> wrote: > honestly, I don't believe that what you describe, are arguments > against the workflow as such --- but rather arguments against waiting > for too long before releasing a new official version. Sage 4.7.2 was > released in last November, Sage 4.8 in January, and now it is March > and Sage 5.0 might still need some care (especially because there are > explicit goals for it, like "OS X 10.7 compatibilty" and "90% doctest > coverage", none of which is reached yet to my knowledge). So there are > (at least) two months between consecutive Sage versions currently. (I > do not know of any plans for some intermediate Sage 4.8.1 release.) > > If there was one (or more) Sage release per month, say roughly "every > 100 tickets at the latest", then I believe all the problems you > mention in your first post were much smaller, maybe gone altogether.
So what you're suggesting is to release stable/"official" versions more frequently, and hence less "development" versions (inbetween), just because the latter (in contrast to the former) aren't based upon each other? ;-) I wouldn't mind having more frequent "official" releases (although a new one every two month to me is pretty ok), but -- sorry -- this doesn't really address the problem. -leif -- 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
