From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeffrey A Law <law@cygnus.com>
To: Joe Buck <jbuck@synopsys.com>
Cc: kriol@fnal.gov, egcs@cygnus.com
Subject: Re: Direct CVS Access to egcs sources 
Date: Sun, 08 Feb 1998 00:29:00 -0000
Message-id: <10721.886926687@hurl.cygnus.com>
References: <199801151801.KAA03652@atrus.synopsys.com>
X-SW-Source: 1998-02/msg00282.html

  In message <199801151801.KAA03652@atrus.synopsys.com>you write:
  > I think that it will have a huge advantage.  Let's say two people send in
  > test reports for the same platform, with the same version, and one has an
  > additional failure.  With cron-generated timestamps, you'll have to search
  > through a whole day's changes to figure out if some patch caused the
  > failure.  With an update-on-every-checkin version, you know they are
  > running identical code and you can start looking for subtle system
  > differences.
  > 
  > You could lessen the problem by doing a new version string every hour,
  > say, but then people may have identical software that differs only in
  >
  > a version number.
How about we continue to bump the version # for snapshots, but change
the "date" string via a nightly cron job?

I just don't see the need at this point to bump the version # at each
checkin -- that (of course) can change if we have a difficult time
interpreting test results.

Does this sound reasonable?


jeff