Next OpenCPN version

[wholybee]

I am curious what the next OpenCPN version will be. It seems from the other threads here that the next version will be a major release, with a lot of changes going on under the hood.

I think it would be a good idea to have one more 5.6.x release to incorporate fixes and minor changes that have already been made in the source before wrapping all those changes into a major release.

One of those fixes, related to the RMB sentence, is one that I am waiting for, as there is a common route for me where I use OpenCPN to follow a course up a windy river.

I am not opposed to compiling it myself, as I have in the past and can compile openCPN from source. But, I am not so sure about working with git to pull the correct branches to have 5.6.2 plus the bug fixes I need. But it doesn't seem like it should be too difficult to pull those together for another interim release.

[bdbcat]

WB...
"One of those fixes, related to the RMB sentence, is one that I am waiting for, as there is a common route for me where I use OpenCPN to follow a course up a windy river."


Remind me, please, about this bug.
Thanks
Dave

[Hakan]

This is supposed to be fixed in Git master and will be included in next O release and in the already announced beta test versions:
"Correct NMEA RMB to comply with IEC 61162-1" #2726
For latest Win beta version see here or else here.

[P_Dub]

Good amelioration in this Windows version OpenCPN 5.7.1+172.e92995d.
Many thanks

[P_Dub]

Once again I am reporting the tidal panel on S57 charts. Speed of current in degree and not in knots.

[wholybee]

Originally Posted by P_Dub

Good amelioration in this Windows version OpenCPN 5.7.1+172.e92995d.
Many thanks

That's fine, but I am not putting a beta version in service as my primary navigation. Never ever. And I am very hesitant to do so with the first 5.7 release. I'll give it a shot, but at the slightest hint of an issue I will back out of it. 5.0 and 5.2 were both "close" but still unreliable and crashed frequently and thus not usable for my primary navigation. I had to back out of both of those releases and stayed on 4.8.8 until 5.2.4. 5.2.4 worked very well. That is why I would rather see another interm release that incorporates developed fixes before a major release that adds features and makes significant changes to the code. I think it is the more responsible course.

[P_Dub]

On some charts it is OK but on some others it is the reverse.

[P_Dub]

All OK for me now. Corrected and no problems at all.