On Tue, Oct 01, 2013 at 10:04:56AM -0600, Eric Blake wrote:
> On 10/01/2013 07:47 AM, Guido Günther wrote:
> >>
> >> - quick smoke test to make sure libvirt and virsh are working:
> >> -- stop system libvirtd
> >> -- sudo ./daemon/libvirt
> >> -- sudo ./tools/virsh list --all
> >> - make check && make rpm && make distcheck
> >> - cd po/ && make update-po
> >> - bump configure.ac
> >> - bump rpm spec
> >> - git tag v$VER -m "libvirt release $VER"
> >> - commit
> >> - git push && git push --tags
>
> Careful - this would push ALL tags, even unsigned tags or tags that are
> local-only. Instead, I would do:
>
> git push && git push origin v$VER
I'm supercautious and use:
git push libvirt.org v0.9.12-maint:v0.9.12-maint v0.9.12.2
>
> which pushes the branch and JUST the newly-created version tag.
>
> >> - git clean -xdf && ./autogen.sh --system && make dist
> >> - upload tarball
> >> - update http://wiki.libvirt.org/page/Maintenance_Releases
> >> - send out announce mail
> >
> > This helped a lot. I hope I didn't mess things up, thanks a bunch!
>
> Looks good; except I don't see the v0.9.12.1 tag pushed upstream yet.
It's here:
http://libvirt.org/git/?p=libvirt.git;a=commit;h=ea095a4aac5ef5166baaa6a98f352651defca5d9
The issue is that (due to an error on my end caused by the failing make
distcheck fixed by 38653834505eaf9d6d6221d90a3e61d5d3d95dbc) 0.9.12.1
wasn't cut from the branch head but from
ea095a4aac5ef5166baaa6a98f352651defca5d9. Now that we have that fixed I
released 0.9.12.2 and everything should be back to normal (and we
hopefully don't need another 0.9.12.x soonish).
Cheers,
-- Guido
>
> --
> Eric Blake eblake redhat com +1-919-301-3266
> Libvirt virtualization library http://libvirt.org
>
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list