Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

So I brought this up in the meeting, but we didn't have time to explore it.

Do we need to maintain the per-commit changelog anymore, or is the per-commit changelog entries spread across GitHub Releases sufficient? (See <https://github.com/pantsbuild/pants/releases>)
Then, if we feel like we _do_ need the full list per-version, could we instead host this on the docsite instead of in repo.

I think keeping this in the releases makes sense.

One of the reasons we had them in the repo was to display them on PyPI, which means embedding them in the wheels, which means rebuilding wheels on every notes change.

And I doubt anyone was consuming the notes in this way

If someone really wants the full list per version - that's what git history is for

What would we do with the human-authored "What's New?" That seems more important

It makes our release simpler if we don't keep the changelog in the repo, so I am in favor