Why is this release numbered 6.4.16? Now there’s a question…

In terms of the underlying LL codebase this is effectively another 6.4.13 release (ie building on the Jellydoll release).

However, to understand why this is a 6.4.16 we need to review recent events. The first point to make is that we have a policy that we usually ship with the release number that matches the underlying LL codebase (unlike some TPVs which tend to ship with the version number after the one they’re based on). We use this principle to make releases easy to understand - LL’s 6.4.13 improved Jellydolls, so Kokua’s 6.4.13 does the same. If we were to use the next number each time there would be the situation where LL release a 6.4.14 with some new features but those features would not appear in Kokua 6.4.14 and only appear in Kokua 6.4.15 which gets confusing for all concerned. More confusingly still, this Kokua 6.4.15 would be lacking whatever gets released as LL’s 6.4.15. And so on…

Having established that principle let’s go over recent events.

(A note for the experts: I have simplified this explanation a bit. LL’s policy is to increment the viewer version number in the source code immediately after any release is done thus while 6.4.14 was on release, the file was set at 6.4.15. Similarly, the file is now set at 6.4.17 so that potential next releases embody that version number. When we merge from LL’s sources after a release occurs we take care to only merge up as far as the commit before the version number gets incremented to begin the next development cycle)

Although there is no new LL code featured in this release there are a number of other new items in this release.

In addition, the RLV and FTRLV versions incorporate RLV 2.9.30.0. Release notes for 2.9.30 are here with original documentation for @setsphere here . Note that while the examples in the documentation will work as expected, there are some subtle differences in the syntax to use as described in the 2.9.30 Release Notes.

There are some other RLV changes beyond those listed in the RLV 2.9.30.0 release notes

All the above are also in Marine’s RLV release. Finally, a Kokua-only bug has been fixed which allowed some IMs to be sent or received when they should have been blocked by RLV.

Release notes

Bug

New Feature

Improvement

Task