Hi
On Slack we add this channel: IntelliJ-platform-tools-releases
for release notifications, what is the equivalent here?
Thereās none yet. Do you have any ideas how this could work here?
No I donāt - I am not familiar with discourse.
I can say what I think where will be the best way for me:
To be notify about new releases- inside the IDE.
Maybe adding a functionality to the DEVkit that listen to external releases of those tools.
Generally speaking about that I think the collaboration module has all the infrastructure needed to create a community messaging inside the ideā¦ but that is probably to the New Ideas topicsā¦
Thanks @jakub.chrzanowski
We still have this channel in JBās Slack instance, so the easiest solution seems to simply c/p all releases quickly over here. Still not sure if and why people are interested, given that Plugin Verifier uses latest release automatically and IntelliJ Platform Gradle Plugin also has builtin up-to-date checks.
@yann.cebron Fwiw, Iād be interested. My logic is as follows: itās nice to know when (and what) changes are happening that might influence builds of plugins to succeed/fail.
For example, letās say that I run a build of my plug-in every hour. Usually it just succeeds, over and over, but then all of a sudden it begins failing. Since, as you say, the latest release is used automatically, it would be great to have a log here of thatās what changed to reference. Imagine I then see a post saying the verifier was released, and thatās what started falling in my build - I could then have a post here to comment on as to what my issue is, and see if others in the community might be having similar issues.
@jakub.chrzanowski just in pursuit of putting an idea out there for further discussion & ideation - what if the discourse had a new category for āIntelliJ Platform Tools Releasesā, and for each new release of a given tool, a new topic was created that included a brief summary+changelog. Ideally the new topic was automated so that it could be created shortly after the release of new versions of the tool(s).
The reason I suggest (a) a new topic for each release, in stead of (b) a single topic for a tool, with a new post/reply within for each release ā is that (b) would just end up with a few topics with a ton of posts, making it possibly harder to follow discussions for specific versions, as everything would be intermingled (and perhaps eventually lead to confusion), whereas (a) would be able to keep the discussions for each release much more contained.
@jgafner 
Hmmm, I do like this idea, Iām just trying to imagine what the UX would look like here. Are you imagining something would constantly be polling for new releases, and when found, would show the developer a notification? Perhaps maybe an inspection or tooltips on hover in a build file in the respective location (e.g. in pluginVerification)?
I donāt know if it can help, but I have a scrapper that displays the latest version of various software: src
- MD report (also available as Atom/RSS feeds)
- For JetBrains IDEs only
It runs as a GitHub action every 4 hrs. When an update is found, reports are updated, committed, which updates the MD reports and Atom/RSS feeds.
I think it would be easy to generate a dedicated report or an Atom/RSS feed that meets your needs.
1 Like
Ha, how funny/ironic! I have a similar project over atā¦
ā¦with a very similar setup (leverage GHA on a schedule to fetch + update as needed). It was created to help our team roughly estimate when new versions (originally of just IU) were going to be released.
I was originally thinking a similar architecture could be setup - a repo to poll for updates/releases from other JB repositories of interest, and then post to this discourse when a new release is found.
But, it seems there is actually a GHA that already exists thatād maybe be better suited to just live in a workflow in each of the respective JetBrains products/tools ā Discourse Topics for GitHub Releases Ā· Actions Ā· GitHub Marketplace Ā· GitHub
1 Like
Just another thought here, Slack only has the past 90 days of messages (aka, releases) so this would not include āeverythingā. Maybe that is enough to kick off/seed this Discourse though? Or maybe for ease, we just start with āreleases after automation is in place for Discourseā? Just putting ideas out for discussion purposesā¦
Iād hope, though, that this is automated the same way the slack channel previously was automated. Just for consistency & ease (Iād hate for someone to have to manually come post for each release 
).
I was referring to JetBrains private Slack instance, where this channel still works.
Ah, I see. Sorry for the misunderstanding, Yann!