djp952
commented
6 years ago One other thought to put out here is that it's possible the changes in Leia will ultimately force a v2.0 with a secondary Input Stream add-on, which would change the plan. If Leia becomes that much of a break from Krypton, both Krypton and Jarvis would end up continuing to use the same code so it would be no more or less difficult to keep them both up to date. In this scenario Krypton and Jarvis would be retired together at some date far off, like 2019.
Jarvis is getting a little long in the tooth at this point. My research into the downloads from here in GitHub indicates that it's still a rather popular platform, approximately 1/4 of everyone is still using Jarvis, which is unexpected.
So far there has only been one appreciable 'feature' that couldn't be implemented on Jarvis, and it was a fringe case option to disable reporting real-time streams (v1.2.8), otherwise everything still works pretty much the same, so I think this boils down to just drawing a line in the sand, per se, and deciding on a last version for Jarvis.
Perhaps when Leia is released formally bump Krypton and Leia up to version 1.3 or 2.0 and keep Jarvis on 1.2 as a 'maintenance' thing, only fixing bugs but not adding anything new?