12 Jan
2022
12 Jan
'22
4:49 p.m.
Hi Neels,
On Tue, Jan 11, 2022 at 06:58:33PM +0100, Neels Hofmeyr wrote:
I fear that we are currently doing the same thing that
we discourage everyone
else from doing: keeping an important branch on the side and not upstreaming it.
There is recurrent overhead on rebasing the branch.
I'm sorry it is that way, but the fact is that we have a large number of projects
with ever-growing scope while the amount of contributors and developer resources
(both inside and outside of sysmocom) is getting lower.
I think the reasoning for completing that codecs work
and merging the branch is
compelling. Can we somehow achieve that before OsmoMSC diverges further?
I think the main problem is that there is no automatic testing for the voice bearer
/ user plane, so we will not catch any regressions if merging a larger patchset/branch
unless at least one, better multiple people sit down and manually test through the
many permutations/situations of codec configurations and check if the audio works.
I could start maybe by holding a talk on it in an
OsmoDevCall?
As readers of this list will have noticed, that OsmoDevCall has now been announced
for this Friday. Looking forward to it!
--
- Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)