Release Notes on Software Upgrades?

sorry, but we do not release that info.

Is there reason why? How do we know what bugs have been fixed? Trial and error by the end user? With the last release being a beta, I think it would only be right to work together between the team and consumer on what works and what needs fixing by including a list of fixes/bugs on releases, especially a beta! Unless everything is being fixed on the next release?

Simply put, the “Beta” release is not a true beta release like other software. The beta label gets added to a release when it is put out in between two set release dates. In example, if we are set to release in Oct and Dec….something comes up that we need to fix right away or need to add (Window8 drivers for example would be released as soon as we get them) we would then release a November release, but it will be called Nov_Beta This is more for our tracking of the software than the end user side. Yes, typically a beta is something that you would test, work back and forth with the development team, but this is not a typical beta. It is simply a label for release that was not scheduled. I will look into getting release notes, but typically we do not release them

Thanks JW! I appreciate your effort. Trying is better then a simple NO. It be awesome knowing what has been fixed in each release. Thank you for also explaining the "beta" releases as compared to other program betas.

do what i can