Alex Hudson
2009-08-19 09:28:29 UTC
Hey everyone.
Our irc logging and building is back in business, to some extent, so for
the first time since we switched to CMake we have the automated tarballs
coming out again. The build bot automatically a. builds from SVN and b.
creates a tarball and builds that too, so any tarball up there has
compiled on at least one machine in the world.
0.6 is late - as usual with all our releases :) - but I've branched SVN
to start the 0.6 releng. For now, continue to commit patches to trunk:
if there are any major changes then use an experimental branch,
otherwise if there's something which shouldn't hit 0.6 let me know and
it won't get merged across.
Automated tarballs of the 0.6 branch will appear here:
http://logs.bongo-project.org/builds/tarballs/branches_releng-0.6/
The file name is bongo-releng-0.6.tar.gz, the first 0.6 release tarball
will be bongo-0.6.0.tar.gz as per usual.
I don't think there are many changes left before we do 0.6. It simply
needs more testing - particularly of upgrades from 0.5.3 to 0.6, which
I'm sure don't work yet - and we may do something about the logging
before 0.6 is out.
Cheers
Alex.
Our irc logging and building is back in business, to some extent, so for
the first time since we switched to CMake we have the automated tarballs
coming out again. The build bot automatically a. builds from SVN and b.
creates a tarball and builds that too, so any tarball up there has
compiled on at least one machine in the world.
0.6 is late - as usual with all our releases :) - but I've branched SVN
to start the 0.6 releng. For now, continue to commit patches to trunk:
if there are any major changes then use an experimental branch,
otherwise if there's something which shouldn't hit 0.6 let me know and
it won't get merged across.
Automated tarballs of the 0.6 branch will appear here:
http://logs.bongo-project.org/builds/tarballs/branches_releng-0.6/
The file name is bongo-releng-0.6.tar.gz, the first 0.6 release tarball
will be bongo-0.6.0.tar.gz as per usual.
I don't think there are many changes left before we do 0.6. It simply
needs more testing - particularly of upgrades from 0.5.3 to 0.6, which
I'm sure don't work yet - and we may do something about the logging
before 0.6 is out.
Cheers
Alex.