On Jan 16, 11:13 am, Jeroen Demeyer <[email protected]> wrote: > On 2012-01-16 11:57, Dr. David Kirkby wrote:> I think if you produce a > different version, then it should have a
> > The whole idea of making "beta" releases public is for people to be able > > to report bugs. > > Of course people can report bugs, but only for *released* development > versions. Was I that unclear? FWIW, I misinterpreted your email in exactly the same way David did. So we now have a system where a Sage tarball one downloads may be "released" or "unreleased", and (independently?) it may be "rc", "beta", "alpha" or even "prealpha". I fear this will become hopelessly confusing for ordinary developers (i.e. those who are not involved in release management on a day-to-day basis). Couldn't we reserve prealpha/alpha for unreleased versions, and re-christen them as betas when they are "released", so there's always a canonical latest beta which would be the natural one to use for general development work and general bug-reporting? Regards, David -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
