On 27 Mai, 01:11, William Stein <wst...@gmail.com> wrote: > On Wed, May 26, 2010 at 4:06 PM, leif <not.rea...@online.de> wrote: > > On 27 Mai, 00:08, Tim Daly <d...@axiom-developer.org> wrote: > >> [...] > >> There is a choice between releasing often and releasing, > >> say, yearly. Sage releases about every week or two at the > >> moment. The upside of this strategy is that people get the > >> latest version immediately. The downside of this strategy > >> is that people are ALWAYS in update mode and big changes > >> are very hard to manage in a small window (2 days?) > > > Indeed, not to mention testing/quality. > > For Sage, this is simply not true for the majority of *users*. The > vast majority of Sage users could care less that we release new > versions -- most don't even notice or care.
I can't judge this. If it's true, fine. My experience is rather that many people just update (not only) software in general either because they fear missing something or just feel they have to have the latest version (they *believe* to be best/ superior), i.e. rather *not* driven by *functional* demand. In fact, newer versions often introduce new problems, often without any (subjective) advantage to the individual user. (Microsoft was forced to offer a Vista-to-XP downgrade option for example... :D :D :D ) Never change a running system... ;-) > In fact, probably most > just use sagenb.org. Many people on this list might pipe up that > *they* are "ALWAYS in update mode". But the people reading this are > a small fraction of users. > > In fact, even me -- when I'm *using* Sage for my research --- I will > have a copy of Sage for that project, and I will not upgrade that copy > of Sage for months on end. :-) -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
