Hi,
The name floating around so far has been "Osmocom-Cellular". This makes a name and version scheme of e.g.:
Alternatives: Osmocom-CellNet Osmo-CellNet
I agree with Harald, adding the "net" part makes sense if we want to keep osmocombb out of it, "cellnet" sounds good. Not sure if adding a reference to "Infrastructure" could also make sense, such as "Osmo-CellInfra" or "Osmo-CellInfraNet".
It was somewhat agreed that we would collect significant API changes in the TODO_RELEASE text file and bump a version tag
whenever >> a "new release (TM)" would be made ... but we never defined when we >> would do that nor how exactly.
As it may be difficult or tedious to sync/fetch the changes from different project repositories, we could have a wiki page with a list of new added features for each release, and when new stuff is pushed into a given project they could add an entry in the changelist for that project for the next release.
It seems to me we could completely replace individual project versions with the overall release ("17.6.0"), *if* we accept that non-changing projects would have several versions tagging exactly the same code state.
So far I really don't like that idea. It just feels wrong, somehow. I cannot really explain it.
I have to say I'm not particularly against this idea from Neels. It would simplify a lot naming of the versions of all projects.