XABCD News Pro – Release Notes and Change Log

XABCD News Pro - Release Notes
Released March 20th, 2017
Style Changes for Text Objects
The text that is shown in the corner of each screen when you click on the news event will now show you the pending news event names on a font, color and style of your choice. This is very helpful if you're using white backgrounds or want to pick a color that is easy visible. Change the size too!

Style Changes for Text Objects
Pick your own audio alert file. It can be any wav format since this is what NinjaTrader 8 supports. You can easily still take any MP3 and change it into a Wav file online. If you need any help just email the wav file to us and we'll do it for you.

Bar Count Buffer Zones
You can determine how much notice you want before an alert triggers by configuring your buffer zone. This is now done using the # of bars before a news alert. For example if you are on a 15 minute chart with a 4 bar buffer, you will be alerted through your above configured audio alert or a message in your alert log exactly 60 minutes before the news event.

Full List of Features
The product and the list of features can be found here: XABCD News Pro Indicator. This is our XABCD Pro indicator that we have released with many enhancements requested from our users.
Frequently Asked Questions
What are release notes and why are they important?
Release notes are documents that accompany software updates, summarizing the changes, bug fixes, new features, and improvements included in a specific version. They are important because they help users, developers, and stakeholders understand what has changed, prepare for potential impacts, and take advantage of new functionality.
What should be included in release notes?
Effective release notes should include a version number, release date, a summary of new features, bug fixes, known issues, deprecations, and any breaking changes. They may also contain upgrade instructions, links to detailed documentation, and acknowledgments of community contributions.
How do release notes differ from a changelog?
Release notes are typically user-facing documents written in accessible language that highlight the most important changes in a specific release. A changelog, on the other hand, is usually a more comprehensive, developer-oriented log that records every change made across all versions in a chronological list.
How often should you publish release notes?
Release notes should be published every time a new version of your software is released, whether that follows a fixed schedule or a continuous delivery model. For products with frequent updates, teams may batch minor changes into periodic summaries while publishing notes immediately for major releases or critical security patches.
What are best practices for writing clear and effective release notes?
Best practices include using plain language that your audience can easily understand, organizing changes into clear categories such as new features, improvements, and bug fixes, and leading with the most impactful updates. Keeping each entry concise, linking to relevant documentation for details, and including version numbers and dates also help ensure your release notes are useful and scannable.
Frequently Asked Questions
What are release notes and why are they important?
Release notes are documents that accompany software updates, summarizing the changes, bug fixes, new features, and improvements included in a specific version. They are important because they help users, developers, and stakeholders understand what has changed, prepare for potential impacts, and take advantage of new functionality.
What should be included in release notes?
Effective release notes should include a version number, release date, a summary of new features, bug fixes, known issues, deprecations, and any breaking changes. They may also contain upgrade instructions, links to detailed documentation, and acknowledgments of community contributions.
How do release notes differ from a changelog?
Release notes are typically user-facing documents written in accessible language that highlight the most important changes in a specific release. A changelog, on the other hand, is usually a more comprehensive, developer-oriented log that records every change made across all versions in a chronological list.
How often should you publish release notes?
Release notes should be published every time a new version of your software is released, whether that follows a fixed schedule or a continuous delivery model. For products with frequent updates, teams may batch minor changes into periodic summaries while publishing notes immediately for major releases or critical security patches.
What are best practices for writing clear and effective release notes?
Best practices include using plain language that your audience can easily understand, organizing changes into clear categories such as new features, improvements, and bug fixes, and leading with the most impactful updates. Keeping each entry concise, linking to relevant documentation for details, and including version numbers and dates also help ensure your release notes are useful and scannable.
Free tutorials, fixes and setup guides by email. Two emails a month at most.










