Before you continue in this project, I wanted to take a few minutes and talk about the note read release
plan.
So when new versions of note read coming out, the Note Read Development Team has published a very detailed
post here called Release Plan, where you can see when to expect new versions of note read.
You can access this page by going to the note trade to achieve website, click on about and then it
releases right there.
And obviously, depending on when you look at this document, what you exactly see here may be different
to what I have recorded and I'm recording this video in January 2022, when I originally recorded this
course, I used note rate version 1.1.1, and it was a couple of years ago now in January 2022.
Note It is at version 2.1. x 2.2 is coming up later in the first quarter of 2022.
The important thing to remember here is that no read release plan depends on node g as the runtime release
plan.
So for example, for note read version two, the requirement is that you are using the note 12 or later
runtime.
As you can see right here and graphically, this is depicted like this.
So you can see, for example, that the plan by the development team is to release.
Note read version 3.0 some time, say towards the middle of 2022 and that will be using note 16 most
likely as I can see here the two bar overlapping.
So my plan is to keep this course up to date and whenever there is a new release of note read to add
relevant section or lectures at the end of the course and show you how to do the upgrade.
So the first time that I'm doing this upgrade is going to be from version 1.1 of note read to version
2.1 of note read again.
And as you will see, that is a fairly straightforward upgrade.
You don't need to do anything to prepare your flows for the new version of Note Read.
Everything is just going to work fine after the upgrade is completed and I expect that that simplicity
of upgrading note for it to newer versions will continue without having to do any significant work to
adapt your flows to new versions of note read.
But of course that remains to be seen.
And as I said, I will be releasing lectures to show you how to upgrade from one version of note rate
to the immediately next one.
So from 1 to 2 and then from 2 to 3 and so on.
What I mean, not always doing that depends on whether changes are significant or not.
What I may not always do is to show you how to upgrade from a major version of note rate, say, from
version 3.0 to a minor version, say to version 3.1.
The reason for that is that point upgrades again from, say, 3.0 to 3.1 should not break anything in
your flows.
Unlike a major upgrade, say, from version one to version to or from version to Division three may
actually break things, although I don't expect to.
As I said, my experience with upgrade from Vision one to version two is one that did not break anything
at all.
It just added capabilities.
So again, to to recap here, I will be showing you how to do upgrades from between major versions.
So from 1 to 2 and to two from three, but not upgrades in minor version, say from point zero to a
0.1 note rate.
So to conclude here, just be mindful of the no trade release plan as published by the Note Rate Team
and have a look at the end of the course to look for lectures showing you how to do upgrades between
major versions.