It would be useful if the release notes/change log identified which modules
changed, as well as just the change that was implemented. And, if the
module had a header that had the change log for that module, it would be
useful.
release_notes.cs has lots of bug fixes described, but not in much
detail. Example:
//v1.4.4 Released 07/??/05
//
// Bug Fixes:
//
// Issue: X2 TR Sequencing broken.
// Fix: The sequencing was broken with the release of
the new
// hardware code back in Beta v1.3.3. The
X2 pin 7 was
// not switching before the delay. This
has been
// addressed and is now working as
intended.
// Reported by: W0VB
// Coded by: KE5DTO
BUT.. nowhere does it say which module was fixed. Is this in hardware.cs
or hardware_v2.cs? And if so, which routine in hardware.cs? just a few
extra words in the description of the fix can be very, very useful.
If you're tinkering with some part of the codebase, and you want to know if
some change in a new beta drop is going to have an impact on what you're
doing, it's nice to at least know that it might have an effect.
Jim, W6RMK
