ROADMAP - ovos-utils 0.1.0

[NeonDaniel]

Things to do before releasing 0.1.0

• 0.0.37 #208 launch last alpha with deprecation warnings before 0.1.0
• 0.1.0 alpha 1 #204 remove all dead code
• refactor/move_from_utils OVOS-workshop#153 move some stuff to ovos workshop
• https://github.com/OpenVoiceOS/ovos-mark1-utils move mark1 to dedicated repo
• feat/bus_apis ovos-bus-client#66 move some stuff to ovos bus client
• feat/gui_bus_api ovos-bus-client#67 move some stuff to ovos bus client
• refactor/move_from_utils ovos-plugin-manager#196 move some stuff to ovos plugin manager
• decouple concerns from bus/workshop #205
• Update input device checks #81
• refactor/bus_utils ovos-bus-client#68
• deprecate bus utils #207
• drop mycroft-core config location ovos-config#90
• LAST ALPHA #206
• Improve test coverage #2
• Feat/ovos logs script #203

[NeonDaniel]

Planning this release, breaking changes mean we should be certain there is no ~=0.0 dependency reference in any stable package before pushing a breaking change to 0.1.0 unless we've explicitly tested that package with the latest ovos-utils alpha

[goldyfruit]

Planning this release, breaking changes mean we should be certain there is no ~=0.0 dependency reference in any stable package before pushing a breaking change to 0.1.0 unless we've explicitly tested that package with the latest ovos-utils alpha

PAHL is using ovos-utils~=0.0, >=0.0.31a6

[NeonDaniel]

PAHL is using ovos-utils~=0.0, >=0.0.31a6

I think most ovos packages are doing that.. I can see 3 options:

1. Go through those packages and update them for 0.1.0 compat. first (kind of backwards from how this is supposed to work)
2. Go through stable packages and update dependencies to ~=0.0.x
3. Make this ovos-utils 1.0.0 (this would actually follow semantic versioning)

[goldyfruit]

Do we want to keep the PIDLock? OpenVoiceOS/ovos-messagebus#4

[NeonDaniel]

Do we want to keep the PIDLock? OpenVoiceOS/ovos-messagebus#4

I think it's only there for ovos-core backwards-compat.. If we deprecate it here then I think we'd have to port it back to ovos-core until ovos-core 0.1.0

[JarbasAl]

I say we should just stop using it everywhere, but PIDLock can remain here as it might be useful in the future

[JarbasAl]

#237