More details on Release History?

[Craig]

Hi I was wondering if it's possible to find more details on exactly what is changed in each release? In general the list in Release History is very generic and does not necessarily mention what method or API, etc. changed. Competing products will display links to issues or work items included, or at least more details about what code changes were made. And the lists are comprehensive.

For instance, in v9 demos, there is a NEW badge on the Grid -> Export, though exporting has been there for awhile. Reading Release History alludes to:

• Add configuration for CSV export API
• Add configuration for Excel export API

but that doesn't really tell me what is changed or available now. Looking at the docs nothing seems radically new.

Details like that are critical in an enterprise environment when evaluating new features or breaking changes, or to just keep up with what's changing. And if I'm just missing this info somewhere, let me know.

 

[Dimo]

Hello Craig,

Thanks for your feedback. It's a good reason to discuss how we can improve our Release notes. We have thought about this in the past, but I am not aware of any specific decisions or plans.

With regard to exporting, the new feature is the ability to provide export options to the export methods. See the Grid programmatic Excel Export documentation and example

Regards,
Dimo
Progress Telerik

[Craig]

I think what you did above would be a good first step IMO. Links to existing items in the feedback portal that drove the work. I know that won't necessarily cover all the changes, especially those you initiate and work on internally. Maybe there needs to be a tag or separate portal where you can have item(s) that list the details of what was worked on. I assume there is some sort of project mgmt or story tracking software you use internally, which obviously you don't want to expose all of that. And may be cumbersome to create separate items for release notes, but it definitely would have value for end users IMO. Obviously you'd have to find the right balance. But if you browse competing products and their release notes you'll see the kind of info that is useful IMO.

[Nadezhda Tacheva]

Thank you for your additional feedback, Craig!

We will take that into consideration when working on improving the flow.