Hello,
For those that don’t know, we have a weekly call to discuss Eclipse Kura development [1]. In addition to this call, I will also post the meetings notes to this mail list. Below is a summary of our last meeting.
- Kura 3.0.0 due by Red Hat Summit (Boston, May, 2-4 2017)
- The Kura 3 API will be backward compatible. Review info at
https://projects.eclipse.org/projects/iot.kura/releases/3.0.0
- API breaking changes postponed to Kura 4
- Create Wiki page describing the API deprecation policy and breaking changes that will be introduced with Kura 4
- Kura 3.0.0: add more @deprecated tags
- Kura 3.0.0: Kura Wires: document the threading model
- Kura 3.0.0: Kura Wires: implement FIFO component and breadth-first graph visit
- Kura 3.0.0: Drivers: waiting for Moka 7 CQ being approved and submit Siemens S7 driver
- Kura 3.0.0: Drivers: submit driver read optimizations
- Kura 3.0.0: the default behavior by the Kura ConfigurationServive is to only track ConfigurableComponent and SelfConfiguringComponent services. Old behaviour can still be enabled
via system property
- Kura 3.0.0: PR #1148: we need JMX integration enabled by default (needed by most Camel components). Describe how to create Java 8 SE Embedded JRE supporting JMX.
- Kura 3.0.0: Review and retarget issues and PRs
- Kura 3.0.0: QA single validation spreadsheet format. Switch from xlsl to open odf format. Check if it can be used with Microsoft Office
- PR #1137: Retarget for Kura 4
- Retarget PR to move org.eclipse.kura.core.util outside org.eclipse.kura.core bundle
- PR #1140: wait Jens review before merging
- PR #1151: retarget for Kura 4. However it should be split in two PRs:
- Jetty to replace the custom event stream implementation
- Support for IE
- Discussion on where/how to archive QA results
[1]
https://calendar.google.com/calendar/embed?src="">
Thanks,
--Dave
