On Mar 18, 3:56 am, Robert Bradshaw <rober...@math.washington.edu> wrote: > Actually, I think all such posts belong on sage-release; all 1000+ > subscribers to sage-devel don't need to know every time Sage alpha X > builds or brakes on system Y. (Of course, these replies are invaluable > for the release manager, so I don't want to discourage people from > sending them in.) Fortunately all such posts usually occur in one > thread, so I can delete them in bulk when they show up on sage-devel. >
All well and good, but I sometimes get the sense that no one is actually checking sage-release. For instance, as of now, the thread "Sage 4.3.4.rc0 released" on sage-devel has 11 replies, while the same thread on sage-release has none. So why should David (and why should I) bother posting to sage-release? The concept of separate mailing lists seems to be working in some cases (sage-combinat-devel is quite active, sage-nt somewhat less so) and not others (the last post to sage-finance was a spam from 6 months ago). I think the Windows port is a special case, since it involves issues quite apart from the rest of Sage development. But Solaris != Windows, and if it is going to become an officially supported system, then now is precisely *not* the time for a separate forum. What might be appropriate is a division between general Sage development and build system issues. The latter would include all the Solaris traffic, and probably everything currently posted on sage- release (including all the "Sage-x.y.z.alpha/rc released" threads). In fact, it might suffice to change the same of sage-release to something like "sage-build"! Kiran -- 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
