Crafting a new GA/RC Post
GA and RC posts will come directly from the Product Manager for the product in question. As these are blog posts, they must be sent through content review.
Title
If your product does not have an official acronym, use the full name only (i.e., “SQL Sentry”). Version should be in standard format for the product in question (typically YYYY.QQ).
The title should be in either of the following formats:
| Breakdown | Title Format | Example |
|---|
| Product with Acronym / GA | <Full Product Name> (<Acronym>) <vvvv.vv[.vv]> is Now Generally Available! | Database Performance Analyzer (DPA) 2022.14.11 is Now Generally Available! |
|---|
| Product with Acronym / RC | <Full Product Name> (<Acronym>) <vvvv.vv[.vv]> RC# is Now Available! | Network Performance Monitor (NPM) 2022.55 RC3 is Now Available! |
|---|
| Product w/o Acronym / GA | <Full Product Name> <vvvv.vv[.vv]> Is Now Generally Available! | Patch Manager 2022.99 is Now Generally Available! |
|---|
| Product w/o Acronym / RC | <Full Product Name> <vvvv.vv[.vv]> RC# is Now Available! | SQL Sentry 2022.27 RC2 is Now Available! |
|---|
Body
Within your product Newsroom, create a new post. On the new GA/RC release page, put in the contents as typical, including links to any platform and product release notes, other supporting documentation, list of new features/enhancements, feature requests that have been implemented, or other notable content.
Tags
For GA posts use (at least) the tag "Generally Available"
For RC posts use (at least) the tag "Release Candidate"
Options
On the Options tab, browse for a file for the Post Image and use one of the pre-approved release-related post images. They are stored here Default Blog Images \ Product Release.
Additional Best Practices
There are several more best practices you can do to encourage a proper feedback loop the community members.
Sign up for notifications
Encourage the customers to subscribe to the newsroom content to stay up to date.
Link to the Product FR’s
Add a link to the product’s Feature Request space for making additional requests.
Call out FR’s that have been Implemented
If Feature Requests directly influenced released elements, update the FR’s status to “Implemented,” put in a status note and link from within the GA post. FR’s in the Implemented status are blocked from voting.
As always, if you have any questions, please do not hesitate to reach out to the Community Team.