bip388: Update Changelog#2144
Conversation
BIP3 clarified the content of the ambiguous Created header and renamed it to Assigned. BIP388 was assigned per bitcoin#1389 (review) on 2023-12-26. The prior "Created:" field content was moved to a Changelog entry.
murchandamus
added
the
Metadata Update
| * '''0.0.1''' (2022-11-16): | ||
| ** First draft. |
There was a problem hiding this comment.
@salvatoshi, if you prefer this to be presented differently, please let me know.
| * '''1.0.0''' (2024-05): | ||
| ** Initial version. | ||
| * '''1.0.0''' (2024-05-12): | ||
| ** Initial version, advance to Proposed (later updated to Complete per BIP3 adoption). |
There was a problem hiding this comment.
See #2143 (comment) for a more explicit alternative for your consideration.
There was a problem hiding this comment.
Thinking about this again, I think it would be a lot of work and add unnecessary clutter to a lot of BIPs to mention the Status update due to BIP 3 adoption on every BIP. I propose that we only lazily mention it in Changelogs when we update them anyway and don’t put a separate line item for it.
I do still want to go through all the Closed BIPs to record the reasons they were closed as planned per BIP3.
There was a problem hiding this comment.
Makes sense.
a lot of work and add unnecessary clutter
Toward the same goal, dropping versioning might be a good simplification for the reasons described in #2145 (comment).
|
cc @bigspider |
Ah thanks, I think I used his Twitter handle instead of his github handle. |
|
ACK Thanks for the updates, LGTM! |
4 participants
This aligns the section title of the Changelog with the proposed best practice from BIP3 (previously "Change Log"), corrects the date in the Assigned header, and adds the missing Version header.
This PR only touches metadata and doesn’t change any of the payload content of the document.
cc: @salvatoshi as Owner to keep you in the loop.