Does Sage have any sort of policy on using "pre-release" software in .spkg files? By this I mean a package which is marked by the upstream developers as a alpha/beta/release candiadate, or something someone has grabbed by use of cvs/jit/svn etc.
I know this is sometimes happens - the Pari update in progress is one such example. In some cases it may be the only sensible option, especially with packages which have not made any stable releases for a long time. A ticket was created to update a package to a pre-release version. One reason cited for doing that was that it contained a feature needed by one particular person. I marked on the trac ticket I felt that pre-release versions should not be used in Sage unless there's good reason - I did not consider one person needing it to be good reason. The actual trac ticket is irrelevant, as now the stable version has been released. But I'd be interested what the views of others are on this matter. It seems to me to be putting a number of people at risk without good reason is a bad idea. Should any desire to update to a non-stable release be discussed on sage-devel first? Dave -- 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
