This page is for release notes for downloadable software. For product announcements, see What's new style guidelines.
To add a release note to the docs site:
- Find the most recent release note for your agent, and make a copy of it in the same folder.
- When you rename your copy, avoid potential version naming conflicts by using a
-separator in your file name. For example, instead of
agent-1-2-3for version 1.2.3 and
agent-12-3for version 12.3.
- Fill in the
version. If applicable, include the
- Using our standard headings for
Bug fixes, add enough summary information in these sections to make a great release note. Link to docs or other resources where they can learn more.
- Commit your changes and submit a pull request. If your release is date-sensitive, make a note in your PR.
A Tech Docs hero will review your release note content and approve your PR to get it published. You can also request others on your team to review your PR.
We build and release the docs site a few times a day, and sometimes builds can take a few hours to complete. If your release is time-sensitive, ensure you've planned for enough time to get your docs live.
Great release notes help users quickly become familiar with your important update, so they know why it matters. Great release notes also help our support and security teams.
By encouraging users to keep current with your latest release, this reduces support time to solve problems on outdated versions. It also mitigates risks if any potential vulnerabilities have been resolved with your latest version.
To write a great release note, be as specific as possible. For example:
- Briefly describe new functionality. Give an example of the value it provides, and link to more detailed information.
- Don't use vague wording such as "various bug fixes." Instead, clearly state what has been improved, so readers will know if an issue they’ve experienced has been resolved.
This information is primarily for the Tech Docs team's use.
To add a new release notes category, update the following areas of the docs site. (You do not need to update the
releaseNoteLandingPage.js files in the
nav/templates folder.) Before you submit your pull request to the GitHub docs site, check that the landing pages and placeholder release note build correctly in your localhost.
/src/content/docs/release-notes, add the following:
- A folder for your new release notes category. The RSS feed link, page format, and date order for release notes listed on this page are generated automatically. For example, see the C SDK category landing page format.
index.mdxfile in your new folder containing the
subjectis the name that will appear on the Release notes landing page.
- A placeholder release note in this folder for the agent team to fill out. If used, the
downloadLinkfield in the release note will be formatted automatically in the published release note.
Before the new category goes live, check with the team's Product Marketing Management (PMM) rep whether they want to include the link in an upcoming What's new post.
/src/content/docs/release-notes/index.mdx, add a new tile section in alphabetical order for your release notes category.
Logos come from
@newrelic/gatsby-theme-newrelic/icons/logo/. If a logo does not already exist for the new agent, use the standard
logo-newrelic icon or an image in
@newrelic/gatsby-theme-newrelic/icons/feathers.js. If you need other options, talk to the team's designer.
Add a link to your new release notes category in the agent's documentation, typically in its
Get started category. For more information, see our documentation about docs in multiple menus.
Optional: Add a link in the agent's landing page text by updating the
index.mdx file in its taxonomy.