Closed GermanBluefox closed 1 year ago
A kind reminder. Is there any reason to delay an update of stable revision?
Feel free to drop a simple note if I should trigger an update.
A kind reminder. Is there any reason to delay an update of stable revision?
Feel free to drop a simple note if I should trigger an update.
Related to https://github.com/pixcept/ioBroker.plenticore/pull/81 I recognized that I should make the labels better understandable. I could do that at the weekend.
Proposed in improvement in https://github.com/pixcept/ioBroker.plenticore/pull/82. Besided that I don't have concern related to an updated stable version.
As adapter 2.2.0 seems to fail with new js-controller 5 an update to 2.3.0 seems to be prior. We did not get an request at ioBroker.repositories until now. Is it OK for you that we update stabel to 2.3.0 anyway?
Please let me know. THANKS
Question: Either the current changes are all not going into 2.3.0 or it needs to be a 2.3.1 because 2.3.0 was already published to npm while ago.
So which to put in the stable repo file?
Thats completly up to you. A version should go to stable after it has been available at latest for some time and the developer thinks theres not bigger problem with it.
To bump a version to stable simple use www.iobroker.dev and open your adapter 'releases' and click at 'set stable' next to desired release.
Alternativly you can update the release menually at ioBroker.repositories within file sources-dist-stable.json.
This issue seems to be outdated.
This issue suggests to update the stable version of this adapter to 2.3.0 but in the meantime an update to version 2.3.1 is suggested.
So this issue will be closed and replaced by an updated one.
Think about update stable version to 2.3.0
Version: stable=2.2.0 (746 days old) => latest=2.3.0 (111 days old) Installs: stable=1244 (82.17%), latest=157 (10.37%), total=1514 Click to edit