Hi @corwin_x
Firstly, my apologies for not providing an update on this issue sooner. I have been head down on some other issues and tasks (not that I am excusing the lack of communication)
We are pushing WD to provide a date when they will have PMS 1.15.0 or newer in their AppStore for all current (PR2100 etc) and EOL (WD My Cloud Mirror etc) so that their old, 1.17.2 update no longer gets offered to users due to it using the wrong “monolitic” version string.
If we were to go back to a monolithic version string, we would need to pad it out so that it would still be higher than the build they offer. See the following example.
When we switched to our new CI, we started over with build numbers. This means that due to a 3 digit build number, are actually a lower version number that what WD offer.
- PMS
1.7.2.3878= WD Version:1723878 - PMS
1.15.0.647= WD Version:1150647
1150647 < 1723878 which would mean you would still be offered 1.7.2.3878 in their NAS App Store as an update.
Now I know we could just wait will we get to 4 digit build numbers and then go back to monolithic version numbers, and that might be fine for now, but that may become an issue down the road if our version numbering scheme changes, or there is another factor we haven’t thought of.
I understand the current situation is an annoying and less than ideal one, but we needed to solve this issue and move to real version numbers at some point, so we chose the move to the or new CI and build/packaging system to do it.
It is unfortunate that getting things resolved on WD’s side has taken this long, but please be patient a bit longer. We have reached out today to push for an update and dates on when this will be resolved.
