The releases are current but also old. Version3 is currently in RC state (and master is reversioned for upcoming v4 work). I expect the v3 release to be tagged within a few days.

Working in production from master is generally hazardous, as it is the staging area for most recent code.

e

> On Feb 27, 2017, at 6:22 PM, Alice Wonder <alice@???> wrote:
>
> On 02/27/2017 05:02 PM, Eric Voskuil wrote:
>>> -----Original Message-----
>>> From: Alice Wonder
>>
>>> Howdy, new to libbitcoin but not new to bitcoin...
>>
>> Welcome!
>>
>>> My interest in libbitcoin, I am creating a payment processing system
>> ... I can't use BitPay or the others because I don't want to put my
>> business at the mercy of another company that can decide they will stop
>> processing payments just because they don't like something I am doing.
>>
>> This is exactly the motivation behind libbitcoin. Web APIs are a
>> centralization force that stand to destroy the Bitcoin security model,
>> not just for individual users but for all.
>>
>>> Anyway the way I run servers, I run CentOS 7 ...
>>
>>> What I have now (don't use, quite alpha packaging) is at
>> http://awel.domblogger.net/7/boost-misc/src/repoview/
>>
>>> I doubt I will contribute any meaningful code to the project but maybe
>> when I am done with the spec files, they will be of use to people on RPM
>> based systems.
>>
>> This is great. We use a significant amount of code generation in all
>> repos and will eventually generate Debian packaging. If you can
>> generalize the CentOS packaging we may be able to incorporate it into
>> the build at some point as well.
>>
>>> Thank you for this project, it solves a lot of things I didn't see a
>> way to solve with the "standard" bitcoin-core project.
>>
>> Great to hear, thanks for the feedback.
>>
>> e
>>
>
> Just figured out (well this morning) that the release tarballs on github seem to be old, and that master has much newer versions.
>
> Is it recommended to ignore the "releases" on github and just build from master?