On Sun, Aug 28, 2016 at 11:53 AM, Sean T. Allen
One small thing we messed up post 0.3.0 release:
After Kevin cut the release, PRs were merged without updating the CHANGELOG, so for example...
The cpu pinning PR its listed as being in 0.3.0 but it is actually still unreleased.
Once a release is done, all outstanding PRs need to have CHANGELOG updated to move to the
new [unreleased] section.
Additionally, some items that didnt need a CHANGELOG entry would now need CHANGELOG entries
because they become enhancements or bug fixes for a now released feature.
is a bug fix for ProcessManager. If it was released with ProcessManager, it wouldn't need a CHANGELOG entry.
Now that ProcessManager has been released, this PR needs to have a CHANGELOG entry under "Fixed".
Questions? Let me know.
I almost forgot about this.
Oh git, so good with the handling of text, so bad with semantics.