You are viewing a single comment's thread from:
RE: Steem 20.6 Officially Released: RC System Update and Optimization
Sweet. :)
I did a post with my thoughts as a consensus witness with regards to v0.20.6rc1 which may still apply here based on the issue tickets and PRs involved. What's the most effective way to engage with the Steemit developers on these questions? Should we add comments and questions to Github? I imagine responding to 20 (or more) individual blog posts by witnesses may not be possible or the best use of the core devs' time, so I'm looking for feedback on what does make sense. Thanks!
We'll announce future releases here before they happen and will welcome questions from witnesses in the lead-up to release.
What is the best format and process for getting those questions to the team? In this case, I've blogged them (as other witnesses have also), but would Github be a better place for lead-up to release questions? I see some activity on the SteemCommunity repo including questions about how to test certain features. Will that be monitored by the core dev team? I think many of us are willing to work with whatever process works best for the Steemit, inc developer team. Thanks for continuing to improve the process of communication with the witnesses and community.
GitHub is usually best for specific questions on stories the team is working on. General questions about the release would probably be best asked in the release announcement thread so everyone can benefit from the answer.
We don't currently follow activity on SteemCommunity as a team but we do read and listen to a lot from the community from many sources. It isn't always practical to respond but feedback is very appreciated and very useful.
Excellent. Thank you. :)