Re: [PATCH] Specify policy for use of revision IDs in version numbers
On Sat, Apr 30, 2011 at 03:51:15PM -0700, Russ Allbery wrote:
> Ben Hutchings <ben@decadent.org.uk> writes:
>
> > + <p>
> > + The upstream version number must not include a non-linear
> > + revision ID or hash, since it cannot help in ordering
> > + versions and it tends to result in very long version
> > + numbers and filenames. This information may be recorded
> > + in the changelog instead.
> > + </p>
>
> I don't think it's Policy's place to tell people that they can't use
> hashes because they *might* result in long version numbers. They usually
> don't.
>
> If we have a version number length restriction, or an overall filename
> length restriction, we should just say that, and point out that using
> hashes may make it hard to meet the restriction.
+1. otherwise, this seems more like a guideline that ought to be in
the developer's reference rather than enshrined as a MUST in policy.
sean
Reply to: