11-03-2020 02:37 PM
Maybe I’m just missing something but as far as I can find these release notes are static and not kept up to date with known issues
example - https://docs.aerohive.com/330000/docs/help/english/documentation/6.5r12_HiveOS_ReleaseNotes.pdf
I learned today via a GTAC ticket, that there is currently an open CFD for the very issue I submitted a ticket for.
I’ve spent time investigating, troubleshooting, collecting documentation and submitting a ticket only to be told it’s a known issue and will be fixed in the next release. Why not publish known CFD’s for firmware so I don’t have to waste time on known issues?
04-25-2022 10:34 AM
03-30-2022 09:09 AM
03-29-2022 07:25 PM
03-29-2022 01:47 PM
Hey guys, it's not that your comments are going unnoticed, I just try not to give you any fluff updates and we're still working on this process, as you can see. I really appreciate the recent examples, that helps a lot with internal discussions about this.
Looking at CFD-7525 specifically, and I do realize this doesn't address the larger concerns here, that wasn't included in the release notes because it's still listed as an unverified bug. That could be because our engineers couldn't replicate it, but we found a fix for the original environment with the issue, so we published the fix just in case it helps others down the road.
All that said, I hear you about not being able to make informed upgrade decisions if you can't trust the documentation to give you the full picture. The service delivery team will be talking about this issue again this week, and I will update this thread the moment I have any substantial updates. More examples can only help move things along so please keep adding those to this thread when you can.