You raise an excellent question and it’s the exact thing that I am working on solving. I’ve been working on making Developer Comms better over the last year. I hope I’ve made some improvements over the last 12 months but I admit there is still a lot of work to be done.
You asked about the place where changes pertinent to app developers … are either announced or listed. Currently, I am focusing on the Developer Blog to be that place.
Why the blog?
The blog currently is lower noise compared to the Developer Community which is a place that notices get posted by product teams. However, because of the high volume of topics and replies to topics, announcements can quickly fall out of view.
The blog can be pushed to you via an RSS feed. If you combine that with ifttt.com you can set up a recipe that monitors the RSS feed and sends you an email on any new post.
Additionally, this forum is using Discourse which has RSS feeds for almost everything. However, as I said before there is a lot of noise. I write a weekly series called Ecosystem Roundup where I find announcements and important information and surface it to the blog. See this post as an example.
You can sign up for the Developer Newsletter. Go to https://developer.atlassian.com and scroll down to the Events and News section. There you can see a sign-up form for the Developer Newsletter.
We round up all the news for the past month and send it in a newsletter form. Additionally, we send out important notices when needed.
Developer Twitter Account
@atlassiandev is another good channel to monitor for when we post the latest blog posts.
Where we want to be
Obviously, the current solution is not ideal and takes a bit of work and yes we are not capturing all of the changes and features being released. I am working internally to make product teams aware of the need to communicate changes to devs. I am making some great progress and hope to see an influx of comms coming your way in the immediate future.
However, posting to the blog is not the ideal state. We want to be able to have an area on the site for changelog type of comm whether that be in the product documentation or a separate dashboard. Where ever it’s located we want it to be subscribable so you can get notices pushed to you.
Take our survey on Developer Comms
I was planning on posting this survey on Monday but this thread seems relevant to mention this now. I’d like to survey the ecosystem on how we’re doing with Developer Comms to see if we’re making progress over this time last year. I’d love for you to fill out this survey so we can learn more about your situation and it will allow me to focus on improvements I need to make.