Project

General

Profile

Actions

Feature #5009

closed

Tag first proper release after repository split

Added by osmith about 3 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Target version:
-
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

Related to osmo-gbproxy - Feature #4992: Split osmo-gbproxy from osmo-sgsn into own git repositoryResolvedosmith01/29/2021

Actions
Actions #1

Updated by osmith about 3 years ago

  • Related to Feature #4992: Split osmo-gbproxy from osmo-sgsn into own git repository added
Actions #2

Updated by osmith about 3 years ago

Patch to temporarily disable version check: https://gerrit.osmocom.org/c/osmo-ci/+/22700

Actions #3

Updated by osmith about 3 years ago

  • Subject changed from Tag first release after repository split to Tag first proper release after repository split

As discussed in review of above patch, I've tagged a 0.0.1 version instead. Keeping this issue open for the first proper tag that actually builds against latest libosmocore.

Actions #4

Updated by osmith about 3 years ago

  • Checklist item deleted (re-enable version != UNKNOWN check for osmo-gbproxy)
Actions #5

Updated by osmith about 3 years ago

  • Checklist item wait for new libosmocore tag set to Done
  • Checklist item tag new osmo-gbproxy release (can we do it together with osmo-sgsn, so osmo-gbproxy is only in one of them?) set to Done
  • Checklist item add osmo-gbproxy to OBS latest (osmo-ci.git scripts) set to Done
  • Checklist item create osmo-gbproxy-latest dir in docker-playground, make sure ttcn-3 tests work set to Done
  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Pau tagged the releases, I've added osmo-gbproxy to OBS latest, Harald made the ttcn-3 tests work.

https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-gbproxy-test-latest/

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)