While reading the discusssion about a road map i thing that “developer” have something different in mind tha “users”
In my world a roadmap give me a vision of the upcoming things, not a detailed projekt plan or a feature complete description. And i thing noone will blame anyone if a possible goal is not reached.
Just tell us what you ar working on on a high level. The information that the version number in the skeleton script need to be updated is to most people meaning less
Example Roadmap on a high high level:
By end of 2020 we like to release OH3 with the following new feature
- Support of Java 11
- Get rid off all eclipse connection
- Complete reworked user interface
- Cool analyse feature
- Cooexistane of text and ui based configuration
- a Semantic system to do fancy stuff
- a better rule system to support Python etc.
See below for some more deatils and ideas on …
We like to release an early stage aplha by end of Septemne (Not ready fpr Produktion)
By End of october the UI should be mostly final
and meanwhile we try to upgrade all binding to version 3
Hope this gives a short view how i see a road map. And as i wrote in another thread: I have the feeling that i find more information about OH3 on twitter than in the community.
Sp great job KUDOS to all maintainers.