[asterisk-dev] Unstable releases lately
sobomax at sippysoft.com
Tue Jan 15 12:01:08 CST 2008
Michael Grigoni wrote:
> John Lange wrote:
>> On Tue, 2008-01-15 at 09:45 -0600, Kevin P. Fleming wrote:
>>> John Lange wrote:
>>>> Back at Fall Von 2007, during the BOF session the topic of having a
>>>> daily SVN snapshot available for download was raised and there seemed to
>>>> be agreement that this was a good idea.
>>> Unless these were distributed as patches, it would actually take far
>>> longer for a user to download a snapshot tarball than to just run 'svn
>>> update' on an existing checkout.
>> That misses the point. It's certainly has nothing to do with download
>> SVN is relatively hard to use compared to a tarball especially since it
>> isn't installed by default on many distros.
> Read the [asterisk-bsd] list awhile if you would like to get a feel for
> what hell is like in the greater unix asterisk space at the moment.
> Aside from little interest amongst core developers in the BSD communities,
> SVN certainly isn't canonical on most BSD or other Unix distributions.
> BSD users must rely on a port maintainer or individual efforts for
> handling every change that comes down the pike and frustration is
> rising to the level of discussions of forking or abandonment of the
Hmm, I am not sure what this FUD is based upon. We have at least 1
seasoned FreeBSD developer with write access to the asterisk repository
(Luigi Rizzo), port is maintained very actively and I don't know of any
significant issues with asterisk on FreeBSD.
And I don't believe that daily snapshot will make any measurable
difference either. All those who are inclined enough to actually do
regression testing of unstable code and could improve quality of product
by submitting meaningful bug reports won't have any issues with using
svn, while the rest should really stick with stable releases.
Sippy Software, Inc.
Internet Telephony (VoIP) Experts
More information about the asterisk-dev