At 05:53 PM 1/25/2006 -0800, Heikki Toivonen wrote:
Andi Vajda wrote:
> How about 0.7m-1 ?
If I understand pje's doc correctly, that would be interpreted as
something following 0.7m version. Not exactly what we mean. It would
also preclude there being a post release of m1. '-' seems to be reserved
to indicate a post release.
Any alphabetic sequence that collates before "final" is considered
prerelease, and anything after is considered postrelease. So, to have
prerelease milestones, you must precede the 'm' with a prerelease tag like
'a' or 'alpha' or 'dev', e.g "0.7dev.m1".
A rule change isn't out of the question, but I'd like to see some evidence
that there are other projects using 'm' to denote prerelease milestones,
and ideally the examples should be related to Python in some
way. Conversely, there need to be no existing Python projects that are
using 'm' to denote postrelease versions, or the change can't be done
without breakage.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
