[1805] in Kerberos_V5_Development
Re: Conventions for gnats PR tracking
daemon@ATHENA.MIT.EDU (Sam Hartman)
Thu Sep 26 21:19:17 1996
To: Ken Raeburn <raeburn@cygnus.com>
Cc: "Barry Jaspan" <bjaspan@MIT.EDU>, krbdev@MIT.EDU
From: Sam Hartman <hartmans@MIT.EDU>
Date: 26 Sep 1996 21:19:05 -0400
In-Reply-To: Ken Raeburn's message of 26 Sep 1996 16:27:45 -0400
>>>>> "Ken" == Ken Raeburn <raeburn@cygnus.com> writes:
Ken> I haven't looked at how you're trying to use PRMS/GNATS, but
Ken> we usually put in there all the messages we exchange with
Ken> customers regarding the PR. This generally includes patches.
Ken> If you're doing things differently (only krbdev people
Ken> submitting PRs, or not sending out patches), then logging the
Ken> list of files is a good idea. I'm not 100% convinced the
Ken> version number is needed if the log entry is made around the
Ken> same time as the checkin, but it wouldn't hurt, and it'd
Ken> definitely be useful if the PR change was logged
Ken> significantly after the checkin. It does add more manual
Ken> work to the PR handling process though. We've long wanted
Ken> some way of automating this coordination between the tools.
Ofgen, sending out patches is reasonable. However, there are
situations where we cannot send out patches. For example, we cannot
send out patches to lib/crypto, etc.
--Sam
