Signed-off-by: Eric Blake <eblake(a)redhat.com&gt; --- Pushing under the trivial rule. setup.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/setup.py b/setup.py index 334d7b2..f5c6542 100755 --- a/setup.py +++ b/setup.py @@ -309,7 +309,7 @@ class my_clean(clean): _c_modules, _py_modules = get_module_lists() setup(name = 'libvirt-python', - version = '1.2.7', + version = '1.2.8',

On 08/05/2014 12:26 AM, Jiri Denemark wrote: > On Mon, Aug 04, 2014 at 11:07:00 -0600, Eric Blake wrote: >> Signed-off-by: Eric Blake <eblake(a)redhat.com&gt; >> --- >> >> Pushing under the trivial rule. >> >> setup.py | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/setup.py b/setup.py >> index 334d7b2..f5c6542 100755 >> --- a/setup.py >> +++ b/setup.py >> @@ -309,7 +309,7 @@ class my_clean(clean): >> _c_modules, _py_modules = get_module_lists() >> >> setup(name = 'libvirt-python', >> - version = '1.2.7', >> + version = '1.2.8', > > Shouldn't you wait until 1.2.7 is actually tagged and released before > pushing this change? Oh, I didn't notice that. At any rate, it's still fairly easy to tag an arbitrary commit rather than HEAD as the 1.2.7 release. DV, are you planning on doing the tag? git tag -s v1.2.7 e715a1c86