Branch cleanup

[jim-bcom]

In order to unclutter our git repos, I've made a pass on the branch currently present to see whether some can be deleted.

I've split the list of branches for each modules into 2 categories:

• merged in develop -> remove feature branches, keep official releases
• not merged in develop -> remove obsolete, keep unfinished work

SolarFramework

• not merged
  • feature/EdgeFeatures: keep
  • feature/HoloLens: ? (seems old)
  • feature/MapUpdate: only one commit adding 'na' to a packagedep*.txt for remaken 1.8beta -> merge this and delete ? (
    @granger35, @Firefly35 ?)
  • feature/OptimizedMatches: @duongnamduong ?
  • feature/SFM: work by @Tugdual-LP . @granger35 ?
  • feature/Semantic: bump to version 0.9.5. Keep
  • feature/Stereo: keep ( @nduong: is possible to merge it such as it does not break current state, or is to too soon? This would comply to our trunk-based dev initiative. This would allow to delete this branch, and start a new one for future work.
• merged
  • 0.10.0: Should soon be deleted
  • 0.9.3: Should be deleted. @cutullic would like to keep it as a milestone for the remoting feature. Maybe convert this into a tag instead to prevent new commit from being pushed in that branch ?
  • feature/DatastructureBoW: @duongnamduong remove ?
  • feature/SLAMOptimization: @duongnamduong remove ?
  • feature/UnityWrapper: @jim-bcom remove ?
  • feature/XPCF2.5.0: @granger35 remove ?