RHEL4 also came out in Feb 2005 and is supported until 2017, so if you can't build Sage version X then you are probably not trying hard enough ;-)
On Saturday, September 13, 2014 4:59:51 PM UTC+1, wstein wrote: > > Does anybody know of any concrete examples of "reproducible research > failures" involving sage, in the spirit of the article? I.e. actual > (published?) research math code done in sage version X that can't be run > today (in particular either the api of sage changed a lot *or* nobody can > build sage version X). Sage is nearly 10 years old and I can't think of > any such examples... But it would be helpful to have some so we can > improve. > > I know there are worksheets/snippets of code that don't work in sage 6.3, > but that is different. > > I did have somebody (Peter Sarnak of Princeton) email me specifically > wanting to run code from something I did in 2003, which was lost, but that > was pre-sage. > > On Saturday, September 13, 2014, kcrisman <kcri...@gmail.com <javascript:>> > wrote: > >> 7) The application of software engineering is I feel an important >>> thing. I have tried to argue this before, with very little success, >>> suggesting William buy books on the topic for serious developers. I >>> note that this paper makes the same comments. >>> >>> >> I think that many Sage developers are familiar with these (as has been >> pointed out before), but the highly distributed nature of Sage development >> and the fact that no one person can come close to knowing the entire >> codebase makes applying a lot of these principles very hard. The >> consensus-driven model Sage uses also makes this challenging - witness the >> discussion about 0-based versus 1-based permutations... Fred Brooks has >> some good comments about the "bazaar" method of development in The Design >> of Design, though I don't necessarily agree with everything he says there; >> his point about many supposedly "bazaar" projects starting with (or >> continuing with) a very clear vision and design from one person is spot on, >> and I think that some modules in Sage that have been shepherded largely by >> one or two people for a long time show this. It would be nice in >> principle, but in practice there are a lot of constraints - mostly time and >> the desire to get actual math in Sage - that make stopping all Sage >> development until everyone has had a proper course in software engineering >> hard. >> >> - kcrisman >> >> -- >> You received this message because you are subscribed to the Google Groups >> "sage-devel" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to sage-devel+unsubscr...@googlegroups.com. >> To post to this group, send email to sage-devel@googlegroups.com. >> Visit this group at http://groups.google.com/group/sage-devel. >> For more options, visit https://groups.google.com/d/optout. >> > > > -- > William Stein > Professor of Mathematics > University of Washington > http://wstein.org > wst...@uw.edu <javascript:> > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
