Dear Kuksa-Dev team,
if you follow the Eclipse iot-pmc discussions lately, you may have noticed that pull-requests are not solely eligible as merit statements for the Eclipse committer election process. An update on the initial contributors list is not possible, hence, we need to have more precise merit statement data for the election processes. For the Kuksa App Store, merged LOCs could be sufficient with the remark of a “significant” contribution - since we’re almost there (merging the PR), the corresponding nomination could succeed afterwards. In general, we need to collect fixed bugs, newsgroup postings, dev-list discussions, or wiki-pages entries etc. This also holds for the planned Kuksa network IDS and Kuksa direct access API contributions.
Apart from that, please have a look at some of my notes taken at last week’s meeting in Turkey:
The first milestone release will be tagged as soon as we have the Kuksa App Store merged and the cloud setup scripts available. The initial idea of regular releases is to have them on a half year basis. Versioning should follow the semantic versioning approach, i.e., - MAJOR.MINOR.PATCH
- API changes will be reflected as MAJOR versions (e.g. 0.0.1 => 1.0.0)
- New features / functionality in a backward-compatible manner come with MINOR versions (e.g. 0.0.1 => 0.1.0)
- Bug fixes will be declared as PATCH changes (e.g. 0.0.1 => 0.0.2)
The first milestone release will contain: - InVehicle
- AGL build scripts
- Vehicle2Cloud APP
- ELM327 Data Feeder for w3c-visserver
- Direct Access API
- W3C-Visserver API
- HawkBit Client
- IDE
- Eclipse Che based IDE setup
- Yocto support
- Target definition support
- Cloud
- Initial Appstore (requires a HawkBit server) **ONGOING**
- InfluxDBconnector
- Scripts to setup Eclipse Hono, Eclipse HawkBit, the InfluxDBconnector, and the Appstore **ONGOING**
Please let us know if you have any remarks, ideas, or similar.
Best regards, Robert |