Support #2363
migrate important branches from openbsc.git to new osmo-{msc,bsc,mgw,sgsn}.git
Status:
New
Priority:
High
Assignee:
Osmocom CNI Developers
Category:
-
Target version:
-
Start date:
07/13/2017
Due date:
% Done:
0%
Resolution:
Spec Reference:
Description
Once the new osmo-{msc,bsc,mgw,sgsn}.git repositories are ready for active development use, take a look at all openbsc.git branches, and migrate active important ones over to the new repositories.
History
#1 Updated by laforge about 4 years ago
- Assignee set to neels
- Priority changed from Low to High
#2 Updated by laforge about 4 years ago
- Assignee changed from neels to Osmocom CNI Developers
assigning this to all developers so they can check for themselves.
#3 Updated by neels about 4 years ago
#4 Updated by neels about 4 years ago
so far, mailing list replies indicate these branches:
- laforge/bssgp_fc -> osmo-sgsn
- laforge/gprs-suspend -> osmo-bsc
- laforge/power_control -> osmo-bsc
- fairwaves/master-rebase
#5 Updated by neels about 3 years ago
None of the above branches have been migrated.
laforge, has anything changed about the importance of these branches?
- laforge/bssgp_fc -> osmo-sgsn
- laforge/gprs-suspend -> osmo-bsc
- laforge/power_control -> osmo-bsc
ipse, do you have a plan / suggestion for getting your openbsc.git master-rebase work merged to the new repositories? There is a quite huge amount of patches on there, many of which seem to parallel developments that happened on the master branches...
