[Openal] Issues building OpenAL CVS (GNU/Linux)

[Panne Sven BenQ MD PBM IPM TPS 4]

I think there is a problem with telling people to download from CVS which is
even more severe: Corporate firewalls without any possibilities to route
through them like SOCKS.  And this is just another reason to use Subversion,
which can be used via http(s). :-) But even then I think it would be nice if
we had some dedicated people in the role of packagers. This is how I think
most projects handle releases: If the developers think that the code is fine
and worthy for a new release, a release branch is made. The packagers for
the various platforms build and test the release branch. If bugs are found
during this process, patches are made to the main branch which are merged to
the release branch. If no bugs are found anymore, upload the packages onto a
server. If after the release some bugs are still found, merge some patches
from the main branch, build, test and upload a patchlevel release. Easy
process, but we would need some people who like to take over the task of
being packagers for a platform. Any
SuSE/Debian/Fedora/FreeBSD/Windows/Mac/... people on this list who would
like to volunteer?

Cheers,
   S.

> -----Original Message-----
> From: openal-admin at opensource.creative.com 
> [mailto:openal-admin at opensource.creative.com] On Behalf Of 
> Stephen J Baker
> Sent: Dienstag, 22. November 2005 19:54
> To: wwp
> Cc: openal at opensource.creative.com
> Subject: Re: [Openal] Issues building OpenAL CVS (GNU/Linux)
> 
> wwp wrote:
> 
> > Sorry to ask, but why not publishing (from time to time) 
> some tarballs 
> > of the sources, when you tag the sources or reach a 
> waypoint? It's not 
> > obvious if sources in CVS are compile-able or stable :-). 
> Forgive me 
> > if that topic has already been addressed.
> 
> I think that's a good idea - lots of people get nervous when 
> asked to grab code from CVS.