-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changelog in master since 0.9.10 #2324
Comments
I agree that we need to get the edge docs up to date - I believe the only big one was #2221, which wouldn't have much of an effect unless you have a custom sync. There's also #2113 removing silent I know @caseywebdev also did some internal refactoring of |
I think |
@philfreo I've tagged this for the next release, with the hope of capturing some more changelog/documentation oversights |
We don't usually write changelogs until the release is tagged -- things can still be backed out or revised before then. |
In #2086 we talked about changing that to keep an "edge" change log due to the number of changes that weren't documented between 0.9.2 - 0.9.9... and if things are backed out or revised the log can be updated as well. Seemed like a sensible solution, and it worked well for 0.9.9 -> 0.9.10. |
Sorry I missed it, let's move the conversation over there then... |
Once again (see #2086) I'm doing some debugging and have discrepancies in behavior between the latest release (0.9.10) and
master
(around whenparse
gets called). I haven't been following along closely so I was hoping to see a changelog to know what intentional changes have been made.The text was updated successfully, but these errors were encountered: