SciChart® the market leader in Fast WPF Charts, WPF 3D Charts, and now iOS Charting & Android Chart Components

Welcome to the SciChart Community Forums!

Please use the forums below to ask questions about SciChart. Take a moment to read our Question asking guidelines on how to ask a good question and our support policy

We also have a tag=SciChart on Stackoverflow.com where you can earn rep for your questions!

0
0

On the Downloads page 3.2.2.5631 is listed as the latest version but on the Software Feed page there are two later versions listed (not including the beta version). Are those in fact stable, released versions? Where are the release notes for them?

  • You must to post comments
0
0

Hi David,

To answer your question, we deliver SciChart in several ways:

1. A stable release / installer via the http://www.scichart.com/downloads page

This release has been tested, the installer installed & run and the source-code delivered to source-code customers. We update the release notes at the point of releasing an installer.

It should be safe to download and install minor increments, e.g. 3.2.1, 3.2.2, 3.2.3 contain only bug fixes in between.

2. A nightly build pushed to NuGet

On the page Getting Nightly Builds with NuGet we show you how you can get the latest bleeding edge version of SciChart via our company NuGet feed. We often push fixes to this feed before they are released as an installer and for specific users who have requested a specific bug fix via priority support tickets.

Often these bug fixes are quite obscure but are affecting a specific user’s application e.g. 3.2.3.5695 contains things like ‘Fixed VerticalLineAnnotation rendering 1 pixel to the left’

We do not update the release notes for nightly builds until they are promoted to the Installer (on the downloads page).

A note about Semantic Versioning

We are trying to follow semantic versioning. This means that

  • Patch increments e.g. 3.2.1, 3.2.2 contain backward compatible bug fixes
  • Minor increments e.g. 3.1, 3.2 contain new features but backward compatible (or, easily made backward compatible with a release note).
  • Major increments e.g. 2.x, 3.x, 3.x contain breaking changes / API differences

The build number e.g. 3.2.1.5531, 5722 is simply the version control checkin number. We don’t always increment the patch number until we release an installer.

A note about BETA versions

We have a v3.3.x BETA on the NuGet feed, which is not visible unless you specifically request ‘pre-release in the NuGet package manager console’. We are using this as a sandbox area to dump feature increments and more experimental fixes before promoting to a stable package.

BETA’s are usually published to the interested parties, e.g. a customer requests a certain feature, we build it, publish the beta and notify them. Later, the BETA makes it into a stable release and everyone gets it. I would not recommend installing our BETAs in production software unless you are specifically interested in the features they contain (e.g. you are the one that notified us!)

Hope that helps clear things up.

Best regards,
Andrew

  • You must to post comments
0
0

I wish you would publish the release notes for NuGet releases somewhere. I’m often wondering what’s in them. I just hit a weird issue where the charts completely hung and I’m behind the NuGet version. I’d love to be able to see the release notes and have some idea what was fixed before possibly sending you an e-mail.

  • Andrew
    We kind of do – but only to the Logs on github (source code customers). I agree, it would be a great feature to have (we have been discussing it for years) but priorities … (time / cost) etc
  • You must to post comments
Showing 2 results
Your Answer

Please first to submit.