1
00:00:00,660 --> 00:00:05,820
Before you continue in this project, I wanted to take a few minutes and talk about the note read release

2
00:00:05,820 --> 00:00:06,240
plan.

3
00:00:06,420 --> 00:00:15,390
So when new versions of note read coming out, the Note Read Development Team has published a very detailed

4
00:00:15,480 --> 00:00:21,630
post here called Release Plan, where you can see when to expect new versions of note read.

5
00:00:22,050 --> 00:00:27,770
You can access this page by going to the note trade to achieve website, click on about and then it

6
00:00:27,780 --> 00:00:28,980
releases right there.

7
00:00:29,400 --> 00:00:36,300
And obviously, depending on when you look at this document, what you exactly see here may be different

8
00:00:36,300 --> 00:00:46,410
to what I have recorded and I'm recording this video in January 2022, when I originally recorded this

9
00:00:46,410 --> 00:00:56,160
course, I used note rate version 1.1.1, and it was a couple of years ago now in January 2022.

10
00:00:56,460 --> 00:01:05,310
Note It is at version 2.1. x 2.2 is coming up later in the first quarter of 2022.

11
00:01:05,820 --> 00:01:14,520
The important thing to remember here is that no read release plan depends on node g as the runtime release

12
00:01:14,520 --> 00:01:14,970
plan.

13
00:01:15,480 --> 00:01:25,110
So for example, for note read version two, the requirement is that you are using the note 12 or later

14
00:01:25,560 --> 00:01:26,350
runtime.

15
00:01:26,370 --> 00:01:30,350
As you can see right here and graphically, this is depicted like this.

16
00:01:30,360 --> 00:01:35,970
So you can see, for example, that the plan by the development team is to release.

17
00:01:36,000 --> 00:01:47,190
Note read version 3.0 some time, say towards the middle of 2022 and that will be using note 16 most

18
00:01:47,190 --> 00:01:50,670
likely as I can see here the two bar overlapping.

19
00:01:51,600 --> 00:02:01,590
So my plan is to keep this course up to date and whenever there is a new release of note read to add

20
00:02:01,890 --> 00:02:09,210
relevant section or lectures at the end of the course and show you how to do the upgrade.

21
00:02:10,260 --> 00:02:18,660
So the first time that I'm doing this upgrade is going to be from version 1.1 of note read to version

22
00:02:18,660 --> 00:02:21,270
2.1 of note read again.

23
00:02:21,270 --> 00:02:24,870
And as you will see, that is a fairly straightforward upgrade.

24
00:02:25,500 --> 00:02:34,500
You don't need to do anything to prepare your flows for the new version of Note Read.

25
00:02:34,800 --> 00:02:42,480
Everything is just going to work fine after the upgrade is completed and I expect that that simplicity

26
00:02:42,480 --> 00:02:49,320
of upgrading note for it to newer versions will continue without having to do any significant work to

27
00:02:49,350 --> 00:02:53,400
adapt your flows to new versions of note read.

28
00:02:53,640 --> 00:02:55,440
But of course that remains to be seen.

29
00:02:55,440 --> 00:03:02,640
And as I said, I will be releasing lectures to show you how to upgrade from one version of note rate

30
00:03:02,760 --> 00:03:04,650
to the immediately next one.

31
00:03:04,650 --> 00:03:07,800
So from 1 to 2 and then from 2 to 3 and so on.

32
00:03:08,220 --> 00:03:13,440
What I mean, not always doing that depends on whether changes are significant or not.

33
00:03:13,680 --> 00:03:20,370
What I may not always do is to show you how to upgrade from a major version of note rate, say, from

34
00:03:20,370 --> 00:03:26,370
version 3.0 to a minor version, say to version 3.1.

35
00:03:26,880 --> 00:03:35,700
The reason for that is that point upgrades again from, say, 3.0 to 3.1 should not break anything in

36
00:03:35,700 --> 00:03:36,510
your flows.

37
00:03:36,510 --> 00:03:42,990
Unlike a major upgrade, say, from version one to version to or from version to Division three may

38
00:03:42,990 --> 00:03:46,290
actually break things, although I don't expect to.

39
00:03:46,290 --> 00:03:52,020
As I said, my experience with upgrade from Vision one to version two is one that did not break anything

40
00:03:52,020 --> 00:03:52,440
at all.

41
00:03:52,440 --> 00:03:53,940
It just added capabilities.

42
00:03:55,290 --> 00:04:01,890
So again, to to recap here, I will be showing you how to do upgrades from between major versions.

43
00:04:01,890 --> 00:04:08,790
So from 1 to 2 and to two from three, but not upgrades in minor version, say from point zero to a

44
00:04:08,790 --> 00:04:10,940
0.1 note rate.

45
00:04:11,700 --> 00:04:18,630
So to conclude here, just be mindful of the no trade release plan as published by the Note Rate Team

46
00:04:18,990 --> 00:04:26,490
and have a look at the end of the course to look for lectures showing you how to do upgrades between

47
00:04:26,760 --> 00:04:28,020
major versions.