Publish change logs more frequently #3912
Replies: 3 comments
-
I +1 this as digging through the docs and cross referencing with commits to figure out what changed is just not a good development experience and hurts overall discoverability. Not too mention the sporatic announcements made in ddevs for API changes. There's seemingly no consistency to where API changes are logged or announced. I'd suggest some sort of RSS feed for all relevant changes to the API, even if those changes aren't "breaking" |
Beta Was this translation helpful? Give feedback.
-
What we really need is a true changelog alongside an annoucements page that has what is currently the changelog |
Beta Was this translation helpful? Give feedback.
-
Was about to post a new topic suggesting to create a RSS feed that would perfectly accompany the changelog's page. +1 for @NovaFox161 |
Beta Was this translation helpful? Give feedback.
-
Currently the change log on the dev portal is kept for mostly breaking changes/feature announcements, i feel that the page in its current form is underutilized. It would be great if it wasn't just the big stuff that made its way to the change log, this would allow developers to keep more in touch with the API and allow them to utilize new features or changes no matter how small. This would save having to dig through the docs and cross reference with commits, or keeping an eye on datamine to find out whats what.
Beta Was this translation helpful? Give feedback.
All reactions