Roll new release about zxing-cpp

[Benjamin-Dobell]

Admittedly I'm doing pretty much the bare minimum to keep this project alive - basically just providing a central place for people to submit patches. To me "versions" only really make sense if there is a proper release cycle, which unfortunately isn't something I have time to do. I guess this project is effectively in "maintenance mode" at the moment. Beyond providing a functional barcode scanner library written in C++ there are no real goals for this project. However, I am happy to merge new features etc. if they make sense.

For this reason I'd be inclined to suggest you create a fork of this project in your personal Github account. That way you can continue to pull down from upstream (this project) but add tags, adopt a versioning scheme and make releases as you see fit. When you're adding tarball and source links to the packages just link back to your own fork.

Does that seem reasonable?

[simonschmeisser]

I know this answer comes quite late but I'm currently having the same issue ... ie finding out what exactly zxing is and which fork should be packaged. To me nu-book version looks the most active and which should maybe be concentrated on. They even made a 1.0 release yesterday after me asking: https://github.com/nu-book/zxing-cpp/releases

Not sure how well the actual version number works for you though