'almost stable' track? (was [Asterisk-Dev] backporting persisent queues?)

[Roy Sigurd Karlsbakk]

>> However, it should NOT go into the Stable CVS tree. I would advocate
>> setting up a "stable-backports" directory with patches that people can
>> apply if they wish.
>
> I'm not opposed to this idea.
>
> What I would probably do is create a "patches" directly in the
> asterisk-addons stable branch with a nice disclaimer saying things like
> "Use these at your own risk.  These patches are totally unsupported."  
> I
> just don't want problems related to these kinds of patches to come back
> on me.
>
> I wouldn't add Mark's patch system to stable for a couple of reasons.
> First, it is definitely a new feature, and is not critical to
> functionality.  Two, I don't want to make it too easy on users to be
> able to patch the code.  I don't mind including patches for some
> features, but I would rather people know what they are doing if they 
> are
> going to use them.

How about creat an 'almost-stable' track where nice addons, patches 
etc? FWICS the 1.2 is prolly 6 months away and 1.0 is missing a lot :(

roy