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

Daniel P. Berrange berrange at redhat.com
Fri May 2 14:31:44 UTC 2008


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.

Dan.
-- 
|: Red Hat, Engineering, Boston   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|




More information about the ovirt-devel mailing list