📌 [IMPORTANT NOTE] Project Continue

[steveepreston]

Sadly, as you know, the fluent-reader has been stopped here.

Some guys forked this repo and Improving it here:
https://github.com/FluentFlame/fluentflame-reader

[antisane]

Every link that says "download releases" leads to an empty Release page.

[FrostBird347]

Every link that says "download releases" leads to an empty Release page.

Unfortunately the only option is to compile the program yourself, but they do intend to put out releases in the future: https://github.com/FluentFlame/fluentflame-reader/milestone/1

[CrystalSplitter]

That's correct, but we are working right now on providing continuous binary deployment for Linux and Windows. MacOS is also planned, though testing for it is more difficult.

[antisane]

Then why bother linking to the releases page in your own readme.md? Why not instead say in that file that there are no compiled releases and save people time?

[CrystalSplitter]

Because development takes time, and is done over many, many, steps. And one of the steps to get a working release is to have links pointing to where a release will be when it's released. :)

[antisane]

Because development takes time

No dispute there, but updating a readme takes seconds.

[CrystalSplitter]

We absolutely welcome contributions, so if you're willing to upload a PR for the CD pipeline so that the README is accurate, I'd happily review it!

[yang991178]

Hey folks, thanks for the fork. Closing this issue as I'm planning to continue work on this repo this year. I appreciate the efforts on the community project. However, I do disagree on some of the technical decisions and product directions on the fork project, and it's probably more realistic to keep them separate.

[steveepreston]

@yang991178 Sounds Good
Is it possible that they joins you? we have spoken about some features there

[CrystalSplitter]

Fluentflame Reader was created because we assumed this project was dead. It had several out-standing vulnerabilities and during upgrades there was no progress on integrating external pull requests. Most notable was the usage of the unmaintained Lovefield project in the original Fluent Reader codebase.

We've tried to maintain compatibility with the upstream as much as possible, both so we could integrate PRs and so we could backport changes if the project was ever revived.

However, the latest changes to Fluent Reader are very far reaching (diff-wise), and are not trivial to backport anymore. Additionally, these changes would require human review and re-implementation on Fluentflame Reader's end. Contributing back to Fluent Reader doesn't seem to be a priority for the upstream, so it will not be a priority for our team at this time.