You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the release of beta10 I had the realization that currently were not creating change logs with each release. One recent PR I created had a major breaking change in it that was released without any kind of notice. I realize this is quite a bit of work. But would the community, and @jzabroski consider attempting to maintain a change log and make submitting change log details part of the PR process for new PRs?
That would at least provide a trail of breadcrumbs for users to reference when the project breaks after an update.
The text was updated successfully, but these errors were encountered:
On Thu, Oct 15, 2020, 1:35 PM HamiltonManalo ***@***.***> wrote:
With the release of beta10 I had the realization that currently were not
creating change logs with each release. One recent PR I created had a major
breaking change in it that was released without any kind of notice. I
realize this is quite a bit of work. But would the community, and
@jzabroski <https://github.com/jzabroski> consider attempting to maintain
a change log and make submitting change log details part of the PR process
for new PRs?
That would at least provide a trail of breadcrumbs for users to reference
when the project breaks after an update.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#379>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADNH7ISBB3J7YLICHLZQDLSK4XH7ANCNFSM4SSJI5CQ>
.
With the release of beta10 I had the realization that currently were not creating change logs with each release. One recent PR I created had a major breaking change in it that was released without any kind of notice. I realize this is quite a bit of work. But would the community, and @jzabroski consider attempting to maintain a change log and make submitting change log details part of the PR process for new PRs?
That would at least provide a trail of breadcrumbs for users to reference when the project breaks after an update.
The text was updated successfully, but these errors were encountered: