Skip to content

No CHANGELOG.md tracking behavior changes across already-landed fixes #118

Description

@chonilius

Several closed issues represent real, user-visible behavior changes to deployed-or-deployable contracts: #55 (dust-distribution algorithm), #56 (TTL scaling for far-future deadlines), #57/#58 (crowdfunding support added to escrow and milestones), #60 (internal extend_ttl/require_admin deduplication). None of this is captured in a CHANGELOG.md — anyone integrating against these contracts (starting with mergefi-backend) has to reconstruct what changed and when from git/issue history rather than reading a single chronological summary. Worth starting one now, even retroactively for the changes already listed above, given how much has already shipped at version = "0.1.0" with no per-change record.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programdocumentationImprovements or additions to documentationenhancementNew feature or requesthelp wantedExtra attention is neededvery hardVery difficult task, expert-level effort required

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions