thanks for restoring the namespace.
- Before changing anything, first ask the group
- If a version is released, it's "forever" and must not be changed
- In case we feel the need for a change and have agreed on it, a new version is to be used
- To support the users of our apps, we should try to provide a transform for the upgrade. This won't be possible in any case (new mandatory fields with no sensible default, ...), but we should at least consider it.
Last but not least, please take my apologies for being so lame with answers. My workload in the professional job is quite intense. Not enough, my mother passed away some months before and there is so much to do. All this means, very often I'm just too tired to turn on a computer if I can avoid it.
Different topic, @Wim: once I tried to upload observations into DeepSkyLog. There was an error if the observations contained such with non deep sky objects (planets, comets). When I filtered this stuff away, import worked fine. Maybe you can adapt DeepSkyLog to simply ignore what is not supported as the targetType?
Best wishes and clear skies
Tom