Dispositioning PRs since v 0.5.0 #440
Conversation
SeanCurtis-TRI
force-pushed
the
PR_update_change_Log
branch
2 times, most recently
from
1ddae70
to
25554fc
Compare
There was a problem hiding this comment.
+@sherm1 for review
This isn't code at all. Just listing PRs in the change log. I'll let you decide to what granularity you'd like to delve into the details.
Once you approve the content, I propose we can merge this without necessarily waiting on CI. (Although I still might just for the pretty green checkmarks).
Reviewable status: 0 of 1 files reviewed, all discussions resolved (waiting on @sherm1)
There was a problem hiding this comment.
Reviewable status: 0 of 1 files reviewed, all discussions resolved (waiting on @sherm1)
This is the exhaustive list of all PRs since v 0.5.0, summarized and grouped (as appropriate). This also includes a re-format so that it fits within an 80-column document.
SeanCurtis-TRI
force-pushed
the
PR_update_change_Log
branch
from
25554fc
to
6cf3db0
Compare
There was a problem hiding this comment.
Rebased on top of master. We'll let CI run through and then merge.
Reviewable status: 0 of 1 files reviewed, all discussions resolved (waiting on @sherm1)
There was a problem hiding this comment.
Changed my mind -- given that it's only a change to a markdown documentation file, we'll go ahead and force merge it. This is the final candidate for release 0.6.0 and we'd like to stress test it and can use the time.
Reviewable status: 0 of 1 files reviewed, all discussions resolved (waiting on @sherm1)
This is the exhaustive list of all PRs since v 0.5.0, summarized and grouped (as appropriate).
This also includes a re-format so that it fits within an 80-column document.
This change is