Can't find proper news section/blog/forum regarding Connect IQ releases

The SDK itself ships with a changelog.

- switch to the latest sdk using the sdk manager

- in VS Code, use the command palette (CTRL/CMD-SHIFT-P): "Monkey C - View Documentation" > "README"

Thank you! I don't know why I didn't find it, even if I read whole documentation :tom_cruise:

The readme has all the release notes back to CIQ 0.0.1 ('m not kidding!).  When I get a new SDK, it's the very first things I look at..  To see what was fixed in the new version...

Dr House said:

Thank you! I don't know why I didn't find it, even if I read whole documentation :tom_cruise:

No worries!

Like a lot of things, I think it could be more intuitive and less hidden. There could be links to the readme for each SDK in SDK manager, for example. When you switch to a new SDK you haven’t used before, the SDK manager could ask you if you want to open the readme. Or when the SDK manager automatically downloads a new SDK and asks you if you want to use it, it could also ask you if you want to open the readme. It wouldn’t be too different from how some phone or desktop apps let you know that an update is available, and at the same time, they give you a chance to look at the changelog.

Yeah, I somehow focused entirely on the website docs  And yes, these are great points. It should be stated somewhere in sdk launcher like "What's new in this release" and "Read more information here and here".

Dr House said:

Yeah, I somehow focused entirely on the website docs

I don’t think it’s unreasonable to expect the changelog to be available on the web. The fact that it’s only available locally is kind of weird.

I generally only use the doc in the SDK.  For one thing, it's always the doc for the SDK I'm using, not a newer SDK, or maybe an older one.

Also, I don't need to find a hot spot if I'm away from home.  The doc is available locally.

Who wouldn't open a README that's easy to find?  One that pertains to the SDK you are using?

jim_m_58 said:

I generally only use the doc in the SDK.  For one thing, it's always the doc for the SDK I'm using, not a newer SDK, or maybe an older one.

But here we are specifically discussing the changelog. There’s no problem with viewing a changelog that’s too new (since the changelog goes back to the beginning), you just scroll down to the section that pertains to your current SDK.

I don’t see why anyone would object to having the latest changelog available on the internet, unless they’re arguing for the sake of arguing.

jim_m_58 said:

Who wouldn't open a README that's easy to find?  One that pertains to the SDK you are using?

OP, who didn’t know how to find it. Pretty sure others have asked about this too.

The fact that we’re having this discussion (and similar discussions have been had in the past), proves that it could be easier to find the README / changelog.

jim_m_58 said:

Also, I don't need to find a hot spot if I'm away from home.  The doc is available locally.

Yeah but if you plan to simulate an app and test app settings, you need internet access. In general, internet access is a given in 99% of cases. Did you notice the Garmin Connect app does not work at all without an internet connection? Some have complained about this, but I’m pretty sure Garmin will never change that fact. Obviously the Garmin Connect website doesn’t work without an internet connection, and the old desktop app (Garmin Training Center?) is long gone. Strava doesn’t work without an internet connection either.

Also, for something as lightweight as a text changelog, why would you need to find a (wi-fi) hotspot? Just tether your development PC to your phone and use your phone’s data. Or - here’s a crazy idea - use your phone to look at the changelog.

Also please note I never said the docs shouldn’t be available locally. I also never said that you should be forced to read the docs on the internet.

What I said is that the changelog should be available on the internet (riffing off OP’s statement that they looked for the changelog among the docs on the website). Some obvious advantages:

- it would be indexed and searchable by google

- it would be archived by sites like archive.org

- if someone asks “hey where’s the Connect IQ SDK changelog???”, you could just post a link that anyone can click on, instead of giving ppl instructions on how to do it

What I also said is that the changelog should be surfaced in an obvious way (instead of forcing the user to hunt for it.) Again, when the SDK manager auto-downloads the latest SDK and asks you if you want to switch to it, it could also give you a link to the changelog. This link could point to either the internet version or the local version.