Re: need help learning Ada for a modula-2 programmer

["Randy Brukardt" <randy@rrsoftware.com>]

"Georg Bauhaus" <rm-host.bauhaus@maps.arcor.de> wrote in message 
news:1714405286412767995.744595rm-host.bauhaus-maps.arcor.de@news.arcor.de...
> "Nasser M. Abbasi" <nma@12000.org> wrote:
>
>> Revision history belongs to the source code itself. If you remove it
>> and put it in some separate container such as a database, then you
>> are stuck to having that database along side for ever, and it means
>> no one can see the revisions made to the source code, unless they
>> access and install some additional software and files.
>
> If the authors decide that others should see the revision notes,
> then they can attach them. Release management typically
> relies on corresponding facilities. One form of attachment is
> a text file, Changelog. IMHO that's a good way of organizing
> publicly visible history. I don't have to infer it, then, from all kinds 
> of
> source files.

The public "changelog" has to be a separately maintained document, IMHO. It 
needs to be a summary of important changes, not the detailed changes that 
get documented in the source files. No end-user needs to know "8/31/08 - 
RLB - Corrected comments to reflect Ada 2007 terminology" or "5/13/11 - 
RLB - Renamed Is_Field to Is_Component to reflect Ada RM terminology". We 
also keep lists of fixed bugs and enhancements separately as users generally 
care about one or the other but not both at the same time.

To some extent, this is clearly a YMMV situation. It depends on the ultimate 
product/customer and the team and the managment.

                                 Randy.