Skip to content
This repository has been archived by the owner on Sep 9, 2020. It is now read-only.

pr-template: instruction about updating changelog #1205

Merged
merged 2 commits into from
Oct 4, 2017

Conversation

darkowlzz
Copy link
Collaborator

What does this do / why do we need it?

Adds instructions about updating changelog in the PR template.

What should your reviewer look out for in this PR?

The instruction message and format.

Do you need help or clarification on anything?

Is this good or can it be improved?

@@ -1,6 +1,10 @@
<!--
Work-in-progress PRs are welcome as a way to get early feedback - just prefix
the title with [WIP].

Add the change in the changelog (except for test changes and docs updates).
Please edit CHANGELOG.md and add the change under the appropriate category (NEW
Copy link
Member

Choose a reason for hiding this comment

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

the changelog currently only has IMPROVEMENTS, not all three of these. seems to me like KISS would dictate that we just have IMPROVEMENTS and BUG FIXES as sections, but if you're modeling this after some other changelog that seems particularly effective, i'm happy to defer.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I think we would have new features when the new status is implemented. So, we can use NEW FEATURES then. Let's keep it 🙂

Copy link
Member

Choose a reason for hiding this comment

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

what rule would you apply to distinguish between an improvement and a feature?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

NEW FEATURE = new subcommands, flags, importer support
IMPROVEMENTS = enhancement on existing features and behavior

I see NEW FEATURE as a special section that would be at the top, which could be used to highlight important changes that affect the users. This could be a new way to do something, support for something new or a breaking change to some existing behavior. And IMPROVEMENTS for the rest of the things, that a normal user need not care much.

Copy link
Member

Choose a reason for hiding this comment

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

i still think we'll have some difficulty cleanly applying that rule to cleanly delineate between the two, but as long as we're looking at "NEW FEATURE" as a special section that we use to highlight things, i think it's probably OK.

Copy link
Collaborator

@ibrasho ibrasho left a comment

Choose a reason for hiding this comment

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

LGTM

@ibrasho
Copy link
Collaborator

ibrasho commented Sep 26, 2017

On another note, tests are failing for a weird reason...

Seems like #1221 fixes this.

@darkowlzz
Copy link
Collaborator Author

Rebased!

@sdboyer sdboyer merged commit 67e8678 into golang:master Oct 4, 2017
This pull request was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants