Open tcharding opened 10 months ago
My team encountered an issue while using this in a recent project demo. My colleague and I would like to provide fixes whenever we can. I am a bit confused on how to make contributions and I have a few questions.
What is the status of this crate ? There are a lot of PRs open long ago and I don't know whether they are stale now
What are the priorities for new releases?
Support for recent Bitcoin core release like version 25.0. Is there a minimum Bitcoin core version support? And to support commands that deprecate others? Example, we encountered an error for generating blocks when using Bitcoin core version 25 where the -generate
command is required compared to previous generate
command
https://github.com/bitcoin/bitcoin/blob/c407caa2972191d6a795228fd4bcdcd4be41d4a7/doc/release-notes/release-notes-0.21.0.md?plain=1#L239
https://github.com/bitcoin/bitcoin/blob/c407caa2972191d6a795228fd4bcdcd4be41d4a7/src/bitcoin-cli.cpp#L85
Are there forks that are to be merged to this repo and should I contribute to those? I found https://github.com/apoelstra/rust-jsonrpc while reading a comment on an issue
I believe this can be closed now, before I do can you confirm please @RCasatta that you have write perms (ie., can you edit this post)? FTR @stevenroose added me as a second owner on crates.io already as well.
Thanks
Hey @RCasatta,
If my flurry of activity in this repo is at all interesting to you can you please review? My intentions are:
Thanks man.
I have write perm
This crate is not getting enough maintenance. #313 has been open for two weeks and other crates in the ecosystem are waiting on it. @stevenroose can you please give someone else release permissions on crates.io? @RCasatta already has merge permission here. It makes no sense forking this crate again, outside of the rust-bitcoin organisation just to depend on the fork by crates within the organisation.