Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ChangeLog #93

Closed
jayvdb opened this issue Feb 26, 2019 · 1 comment
Closed

ChangeLog #93

jayvdb opened this issue Feb 26, 2019 · 1 comment
Assignees

Comments

@jayvdb
Copy link

jayvdb commented Feb 26, 2019

Would you mind creating a changelog to make it easier for packagers and other users to understand what is in each release.

Currently the best we have is "Push up to 218904912" at https://github.com/abseil/abseil-py/releases/tag/pypi-v0.6.1 , or manually building a changelog from the commits

@rickeylev
Copy link
Contributor

Yeah, I've been meaning to add one, but wanted to figure out if there is some standard way to do it. Namely a file format and a tool to help populate a file based on commit descriptions.

From some looking around, I found a pretty wide variety of ways people do it.

I guess I'll just pick one.

@rickeylev rickeylev self-assigned this Mar 11, 2019
rickeylev added a commit to rickeylev/abseil-py that referenced this issue Mar 12, 2019
Added:

*   (flags) `flags.mark_bool_flags_as_mutual_exclusive`: convenience function to
    check that only one, or at most one, flag among a set of boolean flags are
    True.

Changed:

*   (bazel) Bazel 0.23+ or 0.22+ is now required for building/testing.
    Specifically, a Bazel version that supports
    `@bazel_tools//tools/python:python_version` for selecting the Python
    version.

Fixed:

*   abseil#94: LICENSE files are now included in sdist.
*   abseil#93: Change log added.

PiperOrigin-RevId: 238053201
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants