I was thinking this would be mostly about non-breaking changes, such as those patches people are already applying manually and running in production.
disagree - breaking change
Quote
Immediate initialisation of RPC + isinitialized in getinfo:
https://github.com/genjix/bitcoin/tree/isinitialized
https://github.com/genjix/bitcoin/tree/isinitialized
disagree - breaking change (people must rewrite their code to expect the RPC server to appear early)
Quote
Name resolution for addresses (genjix@foo.org -> 1kjdskjds3232dsjds4343):
https://github.com/genjix/bitcoin/tree/bitnom
https://github.com/genjix/bitcoin/tree/bitnom
That's more like it
I think this sort of change -- presuming it doesn't break any existing APIs, which I don't think it does -- would be perfect for these "useful patches" nightly builds.Quote
Maybe you could setup a Bitcoin cloud build service? I login... add my branch and click generate builds.
Sounds like a great bitcoin business or website for somebody...