Actions
Feature #5009
closedTag first proper release after repository split
Start date:
02/04/2021
Due date:
% Done:
100%
Spec Reference:
Description
Following up on #4992 (Split osmo-gbproxy from osmo-sgsn into own git repository).
laforge wrote in https://gerrit.osmocom.org/c/docker-playground/+/22636/1/osmo-gbproxy-latest/Dockerfile#34:
yes, but given that there's no osmo-gbproxy tag/release, that is not really relevant yet. And since todays osmo-gbproxy.git depends on tons of unreleased libosmocore.git changes, we won't have a working osmo-gbproxy tag (and hence no package, and hence no test) for quite some time.
It will take a few weeks at least.
This issue is to keep track of what needs to be done after the release (e.g. enable the "version must not be UNKNOWN" check for osmo-gbproxy again, which I'm about to disable now since that is failing).
Checklist
- wait for new libosmocore tag
- tag new osmo-gbproxy release (can we do it together with osmo-sgsn, so osmo-gbproxy is only in one of them?)
- add osmo-gbproxy to OBS latest (osmo-ci.git scripts)
- create osmo-gbproxy-latest dir in docker-playground, make sure ttcn-3 tests work
Related issues
Actions
