Should release notes be more specific?

Author
Post
Essentials Only Full Version
ampfixer
Max Output Level: -20 dBFS
  • Total Posts : 5508
  • Joined: 2010/12/12 20:11:50
  • Location: Ontario
  • Status: offline
2017/02/23 13:59:49 (permalink)

Should release notes be more specific?

Personally, I would like release notes to include specific references to any bugs that are addressed. Rather than saying there's a bunch of fixes and enhancements, I'd like it to say "We fixed bug CWBRN - X". MY logic is that it would show a systematic approach to addressing known issues, and help me decide if I will bother to install the update. When there's no number I have to search for words and descriptions.
 
What do you think?

Regards, John 
 I want to make it clear that I am an Eedjit. I have no direct, or indirect, knowledge of business, the music industry, forum threads or the meaning of life. I know about amps.
WIN 10 Pro X64, I7-3770k 16 gigs, ASUS Z77 pro, AMD 7950 3 gig,  Steinberg UR44, A-Pro 500, Sonar Platinum, KRK Rokit 6 
#1

1 Reply Related Threads
    Brian Walton
    Max Output Level: -79 dBFS
    • Total Posts : 584
    • Joined: 2014/10/24 22:20:18
    • Status: offline
    Re: Should release notes be more specific? 2017/02/23 14:04:35 (permalink)
    It is only an early release at this point, I don't expect the full layout of every detail until it is the actual release.  IMO
     
    And I personally think the description of the bug fix is what most users would be interested in vs some obscure reference number to a bug that quite frankly only a small subset of users even experience.  I'm thinking very few users would track on that level.  
    #2
    Jump to:
    © 2024 APG vNext Commercial Version 5.1