On 16 November 2014 at 17:34, Matthew Jordan mjor...@digium.com wrote:
On Wed, Nov 12, 2014 at 6:44 AM, Leif Madsen lmad...@thinkingphones.com
wrote:
Would it also make sense to require new features be listed in the CHANGES
file for the point release? I don't want to add lots of work here,
On Wed, Nov 12, 2014 at 6:44 AM, Leif Madsen lmad...@thinkingphones.com wrote:
Matt and Community,
This looks great to me. I've tweaked the wiki page a little bit to better
reflect the branch merging since 1.8 is now EOL. Otherwise, I think this
meets a very nice balance between allowing
Matt and Community,
This looks great to me. I've tweaked the wiki page a little bit to better
reflect the branch merging since 1.8 is now EOL. Otherwise, I think this
meets a very nice balance between allowing features in to keep pace with
the industry and anarchy.
I look forward to next
+1
This sounds more than reasonable to me.
Sent from my iPhone
On Nov 10, 2014, at 5:57 PM, Matthew Jordan mjor...@digium.com wrote:
At AstriDevCon, we spent a good amount of time discussing whether or
not we should allow new features or improvements to be made in release
branches. As I
At AstriDevCon, we spent a good amount of time discussing whether or
not we should allow new features or improvements to be made in release
branches. As I summarized previously [1]:
{quote}
Draft a policy for allowing improvements in release branches.
The Asterisk project today does not exist in
