What to do with issues that are only solved in rebis-dev?

[triska]

Dear all, and @mthom especially,

there are increasingly many issues that are already addressed in rebis-dev, yet remain fully or partially present in master, such as for example: #463, #1138, #1148, #1125, #1303, #1305.

So, in addition to its greatly improved performance, the rebis-dev branch also works more correctly than master in several cases of practical relevance, and even has new features that are not present at all in the master branch, such as a on the toplevel to view all solutions.

Therefore, what should we do with these issues, should they remain open until they are addressed also in master, in part as a warning to others that these issues are present in master, and also to prevent duplications of issues that are already addressed in rebis-dev?

Alternatively, would you consider merging the current state of rebis-dev into master so that all these corrections appear in both branches, and then resume development in rebis-dev from then on? Personally, I would welcome such a merge, so that all these issues can be closed as fully addressed. In the past few months, I have used rebis-dev for all Prolog work I did, and found it superior to master in almost every way: The single yet unaddressed regression I found in rebis-dev that does not exist in master is #1185, a rather trivial problem I can easily work around if it were to appear in master.

Thank you and all the best,
Markus

[josd]

rebis-dev works really nice and well for our Webeye project and a merge would be great indeed!

[mthom]

I could merge rebis-dev to master and resume regular development on master. rebis-dev is meant to host widely destabilizing changes that break many things (like changing the heap representation completely).

[triska]

I think that would be awesome! And I hope it would also address #1047!

[mthom]

Yes, I'll tag the new release as version 0.9.0.

[mthom]

OK, all done! Everything is merged to master. Sorry, @triska, I just realized I squashed your latest README changes.

[triska]

Thank you a lot, it's already restored now! Awesome!

[josd]

Excellent and we are very happy with KNowledgeOnWebScale/oko@7a69163