Re: [gtk-vnc-devel] ANNOUNCE: Release 0.3.2 of GTK-VNC
- From: Anthony Liguori <anthony codemonkey ws>
- To: "Daniel P. Berrange" <berrange redhat com>
- Cc: gtk-vnc-devel List <gtk-vnc-devel lists sourceforge net>
- Subject: Re: [gtk-vnc-devel] ANNOUNCE: Release 0.3.2 of GTK-VNC
- Date: Tue, 01 Jan 2008 10:52:16 -0600
Daniel P. Berrange wrote:
On Mon, Dec 31, 2007 at 01:39:10PM -0600, Anthony Liguori wrote:
Daniel P. Berrange wrote:
I was just going to post an announcement to freshmeat.net when I discovered
you had already done so! I didn't realize freshmeat allowed non-project
owners to post release announcements, but thanks for updating it :-)
Yeah, I was surprised myself :-)
I was thinking of making a wiki page to document the whole process of
doing a release just to make sure we were covering everything whenever
we did a release. The list so far seems to be:
1) Update configure.ac
2) Update ChangeLog
3) Update NEWS
4) make distcheck
5) Publish file to sourceforge
6) Announce on gtk-vnc-devel
7) Add freshmeat release
Anything I'm missing?
0) Check the latest nightly build succeeded.
I don't think I mentioned it before, but I have a server which does nightly
builds of the whole virtualization tool stack, of which GTK-VNC is a part.
It basically just runs the 'autobuild.sh' script and publishes the logs,
the SCM changelogs, the RPMs, and overall status. It then builds virt-manager
& virt-viewer aginst the just built GTK-VNC as an extra sanity test.
You can see nightly build status at:
http://builder.virt-manager.org/module-gtk-vnc--devel.html
Very nice!
Regards,
Anthony Liguori
Regards,
Dan.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]