Version number change proposal

[Brian C. Lane]

The current version number scheme isn't a normal N.V.R, I propose to bring 
it in line with other version numbers by using epoch so that versions like 
0.3.3 will be resolved as being higher than 033.

I've built this and installed it locally, here's the koji link:

http://koji.fedoraproject.org/koji/taskinfo?taskID=2560107

diff --git a/livecd-tools.spec b/livecd-tools.spec
index 39956cd..243c230 100644
--- a/livecd-tools.spec
+++ b/livecd-tools.spec
@@ -4,8 +4,9 @@

Summary: Tools for building live CDs
 Name: livecd-tools
-Version: 033
-Release: 3%{?dist}
+Version: 0.3.3
+Release: 4%{?dist}
+Epoch: 1
 License: GPLv2
 Group: System Environment/Base
 URL: http://git.fedorahosted.org/git/livecd
@@ -17,7 +18,7 @@ Source0: %{name}-%{version}.tar.bz2
 # Temporary patch until next livecd-tools rollup
 Patch0: gzip.patch
 BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root
-Requires: python-imgcreate = %{version}-%{release}
+Requires: python-imgcreate = %{epoch}:%{version}-%{release}
 Requires: mkisofs
 Requires: isomd5sum
 Requires: parted
@@ -83,13 +84,17 @@ rm -rf $RPM_BUILD_ROOT

%files -n python-imgcreate
 %defattr(-,root,root,-)
-%doc API
+%doc API COPYING
 %dir %{python_sitelib}/imgcreate
 %{python_sitelib}/imgcreate/*.py
 %{python_sitelib}/imgcreate/*.pyo
 %{python_sitelib}/imgcreate/*.pyc

%changelog
+* Wed Oct 27 2010 Brian C. Lane  - 0.3.3-4
+- Testing change of version and adding Epoch to make sure it is newer
+- Add COPYING to python-imgcreate subpackage
+
 * Tue Jul 30 2010 Bruno Wolff III  - 033-3
 - The previous update got replaced by the python update; another bump is needed.

How does this look? Any objections?

Dependencies look good, these depend on livecd-tools

appliance-tools-0:004.5-1.fc12.noarch
ltsp-server-0:5.1.95-1.fc13.x86_64
revisor-cli-0:2.1.11-1.fc13.noarch
revisor-cli-0:2.2-1.fc13.noarch

I've installed all of them and none complained about the different version 
number.

Brian

[Bruno Wolff III]

On Wed, Oct 27, 2010 at 17:11:41 -0700,
  "Brian C. Lane"  wrote:
> The current version number scheme isn't a normal N.V.R, I propose to bring 
> it in line with other version numbers by using epoch so that versions like 
> 0.3.3 will be resolved as being higher than 033.

Are we going to start creating branches? In the past only tags were used.
If we do branches, would those change with the second digit?