[asterisk-dev] SIP TCP/TLS, release policy and more (personal opinions included)

Kevin P. Fleming kpfleming at digium.com
Mon Oct 20 14:39:55 CDT 2008

` Olle E wrote:

> Every effort I have done of discussing this release policy has been  
> met by
> "you're too late, we won't listen to you" attitude. I strongly wish
> that the project realize the mistake and changes policy again.
> If that won't happen, it's a must to do proper mangement of a boring  
> 1.6 version
> in a branch in svn or elsewhere for the users that will require it,  
> regardless what Digium
> says. Due to trademark issues, we might have to find another name than  
> Asterisk
> for this version, since it will be different from the "official 1.6  
> release".

I'm sorry, but laying all this blame on Digium is just silly. You've
brought this issue up on this mailing list multiple times, and each
time, *community members* have told you that they wanted this new
release policy and that they are on board with it. You make statements
like this as if Digium mandated this policy and forced the community to
take it, when in fact that is not true, and the community (in general)
were quite happy about this new plan, and they have told you that with
their responses. There will always be differences of opinion, but at
some point decisions have to be made, and not rehashed every few months
(time which could be better spent improving code, instead of talking
about improving code).

If a team of community members wants to take responsibility for
backporting bug fixes (non-regression fixes) and releasing 1.6.0.x
releases indefinitely (like the 'stable' team does for the Linux
kernel), I'd be totally on board with that idea, including giving those
people permission to manage the releases themselves and distribute them
as official Asterisk releases from the Digium download servers. Once
again, you've made comments that tend to inflame passions, rather than
just proposing an idea and asking whether the people who have to make
the decision (about whether something can be called 'Asterisk') would
find it acceptable. As long as the changes made in these 'stable'
branches came from other branches (backports, not new development), I
think we at Digium and many members of the community would be very happy
to support such an effort in any way that we practically can do so.

Kevin P. Fleming
Director of Software Technologies
Digium, Inc. - "The Genuine Asterisk Experience" (TM)

More information about the asterisk-dev mailing list