We decided to remove the project tag prefix and just use arbitrary strings for features without validation. But we should add the following to each message sent by the client:
- catagory (= project tag, e.g. ORAVS). Better having a single place instead of duplicating the project tag in each feature name
- version (version of the product/lib). Could be useful to know if there are some older version out there.
Background: Exasols privacy policy (https://www.exasol.com/privacy-policy/, 1.3) allows us to collect this info. Even when “category” does not fit directly (“projectName” or "projectTag" might be better), we should keep that name to avoid confusion.
AC
- Remove project tag prefix from features
- Add category field with value project tag
- Add version field, require version when creating the tracking client
We decided to remove the project tag prefix and just use arbitrary strings for features without validation. But we should add the following to each message sent by the client:
Background: Exasols privacy policy (https://www.exasol.com/privacy-policy/, 1.3) allows us to collect this info. Even when “category” does not fit directly (“projectName” or "projectTag" might be better), we should keep that name to avoid confusion.
AC