[Ovirt-devel] [PATCH] A few specfile tweaks

[Hugh O. Brock]

On Fri, May 02, 2008 at 03:31:44PM +0100, Daniel P. Berrange wrote:
> On Fri, May 02, 2008 at 10:19:24AM -0400, Chris Lalancette wrote:
> > Ian Main wrote:
> > > This patch ups the ovirt rpm version to 0.5 to avoid file conflicts with the 0.4 release.  It also makes ovirt-wui-install install into /usr/sbin instead of /usr/bin.
> > > 
> > > We should really be upping the version every time a file changes.
> > 
> > ACK for this change, but I don't think we should bump the version every time.
> > The reason is that we want the version number to match up with the next release.
> >  What we should probably do is just bump the release number during a development
> > cycle, and then bump the version at the end; that seems to work pretty well for me.
> 
> It is important to distinguish the dev snapshots from the previous stable
> release by version number. Merely bumping the release during development
> does not really achieve this.
> 
> IMHO the way to deal with this is to
> 
>   - Immediately after a release:
>       - Bump the version number
>       - Reset the release number to '0.git1'
>   - When making changes
>       - Bump the last digit in the release number, eg '0.git2', '0.git3'
>   - At time of release
>       - Bump the release to '1'
> 
> This ensures that the RPM has a newer version number to indicate it is
> functionality different from the previous stable release, and using the
> leading '0' in Release: is following Fedora guidlines for pre-release
> software release numbering scheme.

Yes, this is what I was thinking as well... does that imply
incrementing the release number on every commit, though? And if so is
it easier to use e.g. a changeset number in the release number to
avoid having to manually increment the release number?

--H