[asterisk-dev] Asterisk 1.6 Release Management Proposal
Russell Bryant
russell at digium.com
Wed Oct 17 15:47:28 CDT 2007
Dan Austin wrote:
>> 3.1.1 team branches
>
>> For anyone with commit access, this is where large all new developments
>> should go first. This includes any significant new features or invasive bug
>> fixes that need extra testing. The changes should not move into release
>> branches until they are reasonably tested and considered ready for release.
>
> Small grammar question/issue:
>
> ...large all new developments...
> --or--
> ...all new large developments...
> --or--
> ...large all-new developments...
>
> I know what it means, but it reads a little funny as is.
Yes, that is certainly weird. I'll re-word the sentence to say "all new large
developments".
Thanks,
--
Russell Bryant
Senior Software Engineer
Open Source Team Lead
Digium, Inc.
More information about the asterisk-dev
mailing list