OH4 Tasks

[J-N-K]

• Upgrade to minimum Java 17 (PR Raise minimum JDK version to 17  #2994)

Need to be done in this order

• Upgrade to new WatchService (PR Refactor WatchService #3004)
• Change to addon.xml from binding.xml (PR Introduce metadata for all add-ons #3050)

Independent Changes

• Upgrade Karaf to 4.4.x
• Refactor DSL rules to an independent add-on (Issue RFC: Refactor DSL rules to an add-on #3233)

[rkoshak]

Maybe not appropriate to list it here (is there a similar issue for openhab-addons?), but shouldn't the Nashorn addon from the marketplace be brought in to the openhab-addons repo as part of OH 4? Then a decision would need to be made whether or not it should be automatically installed by default (like rrd4j) or not (I'd vote for not, assuming the porting of Blockly to JS Scripting is done before that.)

This seems like a great opportunity to split out Rules DSL into it's own add-on too. I'm not sure that's required for OH 4 though, but I think it would be a good idea.

[J-N-K]

Please note that there is also openhab/openhab-distro#1316 which already covers some of your points. I had a quick look at refactoring DSL rules to an add-on, but that requires a bit more work.

[florian-h05]

assuming the porting of Blockly to JS Scripting is done before that

I expect it to be — I created the code that automatically switches from Nashorn to GraalJS by modifying the MIME type and ported the logging blocks and @stefan-hoehn ported another block categories two weeks ago. You can have a look at https://github.com/stefan-hoehn/openhab-webui/commits/blockly_jsscripting. After the 3.4.0 Stable Release, I‘ve to take care of a few things in openhab-js but I am planning to ported a few other blocks over the holidays.

[cweitkamp]

In the past we tried to use GitHub Projects to keep track of issues and pull requests for separate OH versions ( see https://github.com/orgs/openhab/projects?type=classic ). I am not sure if someone tracked and kept it up to date all the time but maybe we should take a second look into the tool. One advantage is that it can be configured globally to be used with several repositories.

[florian-h05]

Sound like a good suggestion @cweitkamp and IMO would make our lives much easier as we have one central place to track everything that‘s important.

[J-N-K]

I already addd a project. Can you see and edit that?

[florian-h05]

I can see and edit the project: I‘ve updated the view to include the repo and labels, but to hide assignees.
I‘ve also added a second view: a Kanban.

[cweitkamp]

Yes, I can see it an edit it.

[stefan-hoehn]

@florian-h05 Should we put the our blockly jscripting issue to the board as well and add all the tasks that need to be done?

[florian-h05]

@stefan-hoehn
Yes, we should add this. But IMO we should create a new issue in webui, reference the old PR and close the old PR. Discussing at a PR is not so great IMO.
In the new issue we can also add todos and describe our approach.

[wborn]

@kaikreuzer can you make the project public in the settings?

Changing the visibility is restricted to owners when you create one:

[digitaldan]

@kaikreuzer can you make the project public in the settings?

Done.

[kaikreuzer]

Ok, you were quicker - I was just about to do it. 😉

[J-N-K]

Since we track it in the project -> Closed.

[florian-h05]

Why is the project closed??