[2302] in Kerberos-V5-bugs
krb5-libs/66: add API versioning before next release
daemon@ATHENA.MIT.EDU (hartmans@MIT.EDU)
Sun Oct 6 01:33:13 1996
Resent-From: gnats@rt-11.MIT.EDU (GNATS Management)
Resent-To: bjaspan@MIT.EDU
Resent-Reply-To: krb5-bugs@MIT.EDU, hartmans@MIT.EDU
Date: Sun, 6 Oct 1996 01:32:40 -0400
From: hartmans@MIT.EDU
Reply-To: hartmans@MIT.EDU
To: krb5-bugs@MIT.EDU
Cc: tytso@MIT.EDU
>Number: 66
>Category: krb5-libs
>Synopsis: add API versioning before next release
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: bjaspan
>State: open
>Class: change-request
>Submitter-Id: unknown
>Arrival-Date: Sun Oct e 01:33:00 EDT 1996
>Last-Modified:
>Originator: Sam Hartman
>Organization:
mit
>Release: 1.0-development
>Environment:
System: SunOS starkiller 5.4 Generic_101945-37 sun4m sparc
>Description:
In short order, the Kerberos Team should decide whether it
will implement API versioning and if it should do so, decide how to
maintain compatability with Beta 7 while allowing for future
extensions.
I consider this to be a critical issue because without a good
policy for API extensibility, the future utility of Kerberos is
limited.
If this is to be implemented, it should happen before the next
release.
>How-To-Repeat:
>Fix:
>Audit-Trail:
>Unformatted:
