Skip to content

Add 30.x branch and/or v30.0 tag #4

@Sjors

Description

@Sjors

There's already some pull requests on Bitcoin Core that will change the interface:

They are (as currently proposed, but debated...) not breaking changes, but they do change the .capnp files and none of these new methods will work with v30.

I'm also proposing some small breaking changes, timing TBD:

Those change would work on master and v31+ and not with v30.

So it's probably a good idea to follow the Bitcoin Core branch and tag convention here:

  • tag v30.0 since the release is out
  • add a 30.x branch based on what's in master now
    • this only follows interface changes that Bitcoin Core backports (none so far)
  • update master if and when any of the above pull requests are merged
  • explain this structure in the README, maybe have the default instructions recommend the v30.0 tag and v30 Bitcoin Core release.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions