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

[Dirk Heinrichs <dirk.heinrichs@altum.de>]

Randy Brukardt wrote:

> I strongly disagree with this advice. The time to write revision history
> entries is when you are either about to write the code or just finished
> doing so (and more rarely, in the middle). That's when all of the
> important issues are fresh in your mind. It's definitely not at check-in
> time, which occurs after all testing is completed. For the Janus/Ada
> compiler, that means after running the entire ACATS and in-house test
> suites (twice, in Ada2007 mode and Ada95 mode). That's at a minumum 4
> hours later - by which time you're likely to have forgotten half of the
> information that ought to be in the change log.

Is this really the cycle every developer needs to go through? I'd think that 
in this case the long running tests would be performed at a later stage, for 
example when your current change branch is merged.

> It's also important to
> have it in the file if the source is likely to be separated from the
> version control at some point -- which is almost envitable in today's
> world (for instance, when the version control in use is changed).

Which version control is this that you'd change to w/o having proper tools 
for migrating _all_ your data (incl. metadata)?

> IMHO, if your depending on merges, especially automated merges, to keep
> your version control consistent, you're already in trouble. You're
> probably losing a percentage of your team's work every day.

I don't get that one.

Bye...

	Dirk
-- 
Dirk Heinrichs <dirk.heinrichs@altum.de>
Tel: +49 (0)2471 209385 | Mobil: +49 (0)176 34473913
GPG Public Key C2E467BB | Jabber: dirk.heinrichs@altum.de