zero269
Well-Known Member
Thread Starter
- Joined
- Feb 2, 2007
- Messages
- 514
- Likes
- 285
Recommendation for Forum Admins/Moderators…
This recommendation was motivated by my other thread here: (Advice) Beta vs. Production Release which was intended to educate the average user on their differences, expectations and their responsibilities with using a beta version.
Beta releases generally need a more focused approach with reporting issues, unlike the production release. Keep this in mind when reading my recommendations below. This is not recommended for the production release versions.
Beta versions are way more likely to see immediate or expedited corrections than a production release, which is why this method will dramatically benefit the RedFox development, forum admins/moderators and AnyStream forum members alike.
I would recommend that Forum Admins/Moderators create a PINNED thread to report beta release issues by version to help prevent endless threads clogging up the page because of each person's own problem explained in their own unique way.
Thread naming examples:
Many are reporting an issue with the version they are using, not the one that just got release. This helps them see that a new one is active. They can see if their issue has been reported, and then look at the next version to see if they even want to try it out. This is especially important when we see several beta releases in a very short period of time.
When to Pin and Unpin?
This recommendation was motivated by my other thread here: (Advice) Beta vs. Production Release which was intended to educate the average user on their differences, expectations and their responsibilities with using a beta version.
Beta releases generally need a more focused approach with reporting issues, unlike the production release. Keep this in mind when reading my recommendations below. This is not recommended for the production release versions.
Beta versions are way more likely to see immediate or expedited corrections than a production release, which is why this method will dramatically benefit the RedFox development, forum admins/moderators and AnyStream forum members alike.
I would recommend that Forum Admins/Moderators create a PINNED thread to report beta release issues by version to help prevent endless threads clogging up the page because of each person's own problem explained in their own unique way.
Thread naming examples:
- v1142 Beta: Report Issues here.
- v1142 Beta: Reported Issues.
- v1142 Beta Release Issues: Report them here.
- Stick with a naming convention so with each visit, members familiarization is improved.
- Pin ONLY the latest TWO beta release issue threads; unpin any previous ones.
- Users can easily go their beta issue version thread and report their findings and upload their log files.
- This will dramatically reduce the number of duplicate issues being reported for a beta release.
- This will improve member experience with reporting issues and confirming they too are experiencing an issue reported by another member.
Many are reporting an issue with the version they are using, not the one that just got release. This helps them see that a new one is active. They can see if their issue has been reported, and then look at the next version to see if they even want to try it out. This is especially important when we see several beta releases in a very short period of time.
When to Pin and Unpin?
- The goal is to have one beta issue thread pinned when possible.
- It makes sense to PIN the latest beta release issue thread at the same time as the beta release software thread.
- It makes sense to UNPIN a thread based on a 2-week timeline for the older version; or after 1 week of thread inactivity. In other words, two pinned beta issue threads only exist for two weeks maximum. Then it's just the latest version.
- Old Thread: v1142 Beta Release Issues: Report them here. Gets unpinned after 1-week of inactivity or 2-weeks max.
- New Thread: v1143 Beta Release Issues: Report them here. Remains pinned until replaced by another beta version or a production release. It can always be re-pinned if something happens that cause users to revert to a beta version.