release process

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Harald Welte laforge at gnumonks.org
Tue Jun 21 08:39:15 UTC 2016


Hi Max,

On Mon, Jun 20, 2016 at 06:27:49PM +0200, Max wrote:
> To me personally the value is twofold: a) we generate some news which
> might be good thing to attract attention of potential contributors (if
> we won't overdo it :) and b) it makes it clear when some feature is
> "officially shipped" so we have to start paying attention to things like
> backward compatibility.

I completely agree.  The lack of a proper release process with release
announcements, the availability of (signed) tar-balls for the source
code, as well as (possibly) the availability of OBS-built packages for
those releases is a problem.

The question is: Who will volunteer to do that? :)

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)



More information about the OpenBSC mailing list