Correct version tag for Bandwidth channel? #4570
-
|
Hi team, It is great to see that the Bandwidth channel has been added, and we are excited to work with it. Also, looking forward to when it comes out of beta user group and into the main channel roster! My question is that, there are multiple version tags specifically mentioning the channel type, and I am not sure which one to use. Hence, I am a bit confused as to which one to use. We are looking to upgrade from v7.4.2 (AGPL version) for the channel. So, I was wondering if there is a stable release that has the Bandwidth channel integrated (even if only for beta)? In the case we have to upgrade to 8.1.x, what should be the sequence ? e.g. 7.4.2 --> 8.0.1 --> Main Branch off the top? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
The last stable release on this fork was 8.0.1, and 8.1.x is our current development branch. So if you're setting up a development environment then you should pull the latest 8.1.x of all components. We would not recommend running that as a production instance. If you do switch to 8.0.1 on a production instance be sure to review the Additional Use Grant clause of the licence. The next stable release on the Nyaruka fork will be 8.2.x sometime in June, at which point 8.0.1 will be upmerged into the AGPL version. |
Beta Was this translation helpful? Give feedback.
The last stable release on this fork was 8.0.1, and 8.1.x is our current development branch. So if you're setting up a development environment then you should pull the latest 8.1.x of all components. We would not recommend running that as a production instance. If you do switch to 8.0.1 on a production instance be sure to review the Additional Use Grant clause of the licence.
The next stable release on the Nyaruka fork will be 8.2.x sometime in June, at which point 8.0.1 will be upmerged into the AGPL version.