Dear @DavidPackouz and @BrennanSingularSound ,
I know you are doing your best to provide us with cool features. Yet you fail on something pretty basic which is your communication around release deliveries… I could link here countless messages requesting “when this or this will be available”. Not only it blurs generally the content of the topic, but those announcements are pretty sparse and difficult to aggregate…
In a recent topic, Brennan just posted this:
Very appreciated, but:
Why don’t you maintain such a list in a pinned separated topic ? You could even prevent comments on this page, to keep it clean. People willing to comment would simply create a topic to discuss about what they disagree with…
Suggestion about this page content/structure:
The next scheduled release
-
There should be a clear (the clearer possible) description of the next release. Ideally it should be so clear that it could become the changelog of the release as is when you eventually decide to release (I mean the one pushed along the device firmware).
-
Something that would be very appreciated would be to have links to certain topics as well, and if needed along with some comments to specify if the release covers what is requested, fixes or provides a work-around for, or is inspired from… The simple fact to have this link would, in the target topic, generate a backlink to this release post… Thus avoiding the usual noise you can see in every topic like “when will my stuff be available ?”…
-
An estimated release date !! I know things can slide, but you definitely can have an idea of when your next release will be issued. Even as a target, even with just week numbers… You could refine the closer you get from this target date…
Next 2 future releases
-
Content can be a bit fuzzier of course, just featuring big buckets like exactly in the post from Brennan mentioned here above.
-
Links to some topics would be cool too, but it could be of course less engaging, more something like a list of topics potentially addressed by the releases.
-
A very rough date !! The unit could be the month or quarter, whatever you choose, but don’t let your users in darkness !
Long Term Plan
-
Ideas more than content.
-
Links to some topics, but just referring topics as to be studied, or analyzing impact of.
-
No date.
History
Each Time a release is officially issued, you can create then a separated document, like you currently do, and basically cut/paste the content of the “next scheduled release” part into this new document.
Then here you reference this release document from here to keep track of the history of releases.
And you shift all releases up… next cycle…
Let me know what you think about this. I don’t feel like it’s super difficult to put in place. It would clarify a lot the topics, provide your users with the visibility they are eager of, simplify and unify your communication around new features.
Finally I have only one question… When will this be available ?