[1855] in Kerberos_V5_Development
Re: use of gnats "release" field
daemon@ATHENA.MIT.EDU (Sam Hartman)
Wed Oct 16 16:14:21 1996
To: "Barry Jaspan" <bjaspan@MIT.EDU>
Cc: Sam Hartman <hartmans@MIT.EDU>, krbdev@MIT.EDU
From: Sam Hartman <hartmans@MIT.EDU>
Date: 16 Oct 1996 16:11:33 -0400
In-Reply-To: "Barry Jaspan"'s message of Tue, 15 Oct 1996 18:36:39 -0400
>>>>> ""Barry" == "Barry Jaspan" <bjaspan@MIT.EDU> writes:
"Barry> The user community does not have access to browse through
"Barry> the PR database. If they did, very few would take the
"Barry> time to do so before reporting a bug; they would just
"Barry> report it again.
I believe it is our intent to fix this. There have been many
people who have asked for a way to get list of known bugs, and providing this would be useful.
"Barry> If you think the release field should contain that
"Barry> information, that we can format it as "found:<b7>
"Barry> fixed:<1.0>" or somesuch. That is actually what we did at
"Barry> OV, and it lets us do searches based on either value.
The other problem associated with doing this is that the
submitter often doesn't know when the bug will be fixed. Finally, I
don't see us getting organized enough to decide more than one release
ahead of time to decide when things would be fixed, so I think the
priority field is sufficient.
"Barry> Barry
