From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 Path: border1.nntp.dca3.giganews.com!backlog4.nntp.dca3.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!news.bbs-scene.org!weretis.net!feeder1.news.weretis.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.fsmpi.rwth-aachen.de!reality.xs3.de!news.jacob-sparre.dk!loke.jacob-sparre.dk!pnx.dk!.POSTED!not-for-mail From: "Randy Brukardt" Newsgroups: comp.lang.ada Subject: Re: need help learning Ada for a modula-2 programmer Date: Thu, 30 Jan 2014 15:58:24 -0600 Organization: Jacob Sparre Andersen Research & Innovation Message-ID: References: <1714405286412767995.744595rm-host.bauhaus-maps.arcor.de@news.arcor.de> NNTP-Posting-Host: static-69-95-181-76.mad.choiceone.net X-Trace: loke.gir.dk 1391119105 20460 69.95.181.76 (30 Jan 2014 21:58:25 GMT) X-Complaints-To: news@jacob-sparre.dk NNTP-Posting-Date: Thu, 30 Jan 2014 21:58:25 +0000 (UTC) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 X-RFC2646: Format=Flowed; Original X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-Original-Bytes: 2733 Xref: number.nntp.dca.giganews.com comp.lang.ada:184614 Date: 2014-01-30T15:58:24-06:00 List-Id: "Georg Bauhaus" wrote in message news:1714405286412767995.744595rm-host.bauhaus-maps.arcor.de@news.arcor.de... > "Nasser M. Abbasi" 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.