On Wed, Dec 20, 2017 at 3:14 PM, Corey Farrell wrote:
> One thing that might improve this is if releases were merged back to the
> major branch. Currently the commit "Update for 13.19.0-rc1" is on the
> 13.19 branch and tagged as 13.19.0-rc1. I believe that if we added 'git
> checkout 13 && git
I just read `git help merge` again and I think the solution is 'git
checkout 13 && git merge --strategy ours 13.19.0-rc1'. This would
effectively tell git that '13' already contains 13.19.0-rc1, but without
actually trying to pull any changes to 13. This merge would be the
final step of mkrel
George asked that I post some scenarios where this would be useful.
1. You are about to create updated asterisk package and want to quickly
scan the changes to 13 since latest 13.x.0 release to see if anything is
a 'must patch' for your deployments. You can use 'tig' to review
changes for cri
The Asterisk Development Team would like to announce the release of Certified
Asterisk 13.18-cert1.
This release is available for immediate download at
http://downloads.asterisk.org/pub/telephony/certified-asterisk
The release of Certified Asterisk 13.18-cert1 resolves several issues reported
by