Changelog

[ryneeverett]

We pushed 1.8.0 without a changelog to get it out the door.

Perhaps this could be automated with something like: https://github.com/github-changelog-generator/github-changelog-generator

[ryneeverett]

In case this doesn't get done, I'm at least going to try to keep track of major changes for release notes here, though I'll likely forget.

Major Changes

• Top-level bugwarrior command (#882)
• Enhanced configuration validation. (#849)
• Survive service failue. (#825)

New and Removed Services

• Added Kanboard service. (#794)
• Added Azure Devops service. (#808)
• Added Git-Bug service. (#934)
• Removed Megaplan service. (#844)

Notable Changes

• gitlab: Merge requests and todo's will respect default_priority setting rather than being set to 'H'. (#816)
• gitlab: Added distinct default priorities for issues, merge requests, and todo's. (#816)
• gitlab: Query support. (#876)
• gitlab: Exclude archived projects by default. (#938)
• gitlab,bitbucket: Deprecate filter_merge_requests in favor of inverse include_merge_requests.(#881)
• bitbucket: Remove basic auth and update oauth2 workflow. (#888)
• jira: Personal Access Token (PAT) authentication support. (#853)
• redmine: Query support. (#886)
• github: Pull issues by URL. (#898)
• notifications: Add applescript backend. (#948)

[ryneeverett]

After updating the above comment for a while, I don't love this process but find that I can't think of a better workflow for this project.

I find a curated changelog like this useful where a git generated one is in my opinion useless.

But I've always found it a pain to update a changelog in the git work tree -- it either involves pushing commits just to update the changelog (and then there's the PR noise versus direct push dilemma) or pestering contributors to update the changelog themselves (and how do you maintain consistency with lots of people editing such a document?).

At the same time, I don't see any way to consistently remember to update an out-of-tree changelog like this.

I'm open to suggestions.

[ryneeverett]

Resolved by #957. Maintaining a draft pull request is the best compromise I've thought of so far.