Skip to content

Conversation

achow101
Copy link
Member

  • Bump to 28.99 in preparation for the 28.x branching
  • Remove current release note fragments. They've been moved to draft release notes in the wiki.
  • Updated bips.md with missing BIPs that were implemented a while ago.

@DrahtBot
Copy link
Contributor

DrahtBot commented Aug 26, 2024

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Code Coverage

For detailed information about the code coverage, see the test coverage report.

Reviews

See the guideline for information on the review process.

Type Reviewers
ACK maflcko, tdb3
Stale ACK hebasto

If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.

@achow101 achow101 added this to the 28.0 milestone Aug 26, 2024
Copy link
Contributor

@tdb3 tdb3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK b58869f
Left nits, but resolved them in the Wiki page

@@ -1,2 +0,0 @@
- Additional flags "in" and "out" have been added to `-whitelist` to control whether
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: Adjusted this in the Wiki Page. Line wrap issue. Also moved to P2P section.

@@ -1,2 +0,0 @@
- unix socket paths are now accepted for `-zmqpubrawblock` and `-zmqpubrawtx` with
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: Adjusted this in the Wiki Page. Line wrap issue.

@luke-jr
Copy link
Member

luke-jr commented Aug 27, 2024

Bump to 28.99 in preparation for the 28.x branching

This should be post-branching...?

@achow101
Copy link
Member Author

This should be post-branching...?

I don't think it particularly matters since that step has to be done in the 28.x branch too, in addition to the other version numbers being bumped.

Copy link
Member

@glozow glozow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, should also do doc/release-notes/release-notes-27064.md

@hebasto
Copy link
Member

hebasto commented Aug 27, 2024

This should be post-branching...?

I don't think it particularly matters since that step has to be done in the 28.x branch too, in addition to the other version numbers being bumped.

During the previous release cycle, it was done just after the branching off.

UPD. I agree that it does not really matter.

@maflcko
Copy link
Member

maflcko commented Aug 27, 2024

lgtm, should also do doc/release-notes/release-notes-27064.md

Added to the wiki, but still needs to be removed here.

Copy link
Member

@hebasto hebasto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK d3fd608.

@DrahtBot DrahtBot requested a review from tdb3 August 27, 2024 15:16
@achow101
Copy link
Member Author

lgtm, should also do doc/release-notes/release-notes-27064.md

Good catch, removed it.

@maflcko
Copy link
Member

maflcko commented Aug 27, 2024

ACK d3fd608 after typo fix

@maflcko
Copy link
Member

maflcko commented Aug 27, 2024

lgtm ACK 1bf9b70

@DrahtBot DrahtBot requested a review from hebasto August 27, 2024 15:26
Copy link
Contributor

@tdb3 tdb3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

re ACK 1bf9b70

@achow101 achow101 merged commit 1248d0d into bitcoin:master Aug 27, 2024
16 checks passed
fanquake added a commit that referenced this pull request Sep 5, 2024
fa3a7eb lint: Check for release note snippets in the wrong folder (MarcoFalke)

Pull request description:

  It is a common mistake to place the snippets in the wrong folder, where they could be missed. For example #30719 (review) or commit 84900ac.

  Fix all issues by adding a simple lint check.

  Can be tested by reverting a prior commit that violated the rule and then running the new check:

  ```
  git revert 35ef34e
  ( cd ./test/lint/test_runner/ && RUST_BACKTRACE=1 cargo run -- --lint=doc_release_note_snippets )

ACKs for top commit:
  l0rinc:
    ACK fa3a7eb
  TheCharlatan:
    Re-ACK fa3a7eb

Tree-SHA512: 65a13696178aa8f94daa12a767cc74861293c631c19da9ca23c0fd43cedd47e7928d0ef14ad9ad83a434c1ac0e006f5a632ba9679756e071dea65b3cbf927c2d
@bitcoin bitcoin locked and limited conversation to collaborators Aug 27, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants