[37964] in Kerberos
Re: bug reporting
daemon@ATHENA.MIT.EDU (Greg Hudson)
Wed Apr 19 13:16:45 2017
To: Richard Silverman <res@qoxp.net>, MIT Kerberos <kerberos@mit.edu>
From: Greg Hudson <ghudson@mit.edu>
Message-ID: <32108eb2-f072-5189-91a5-879041dd3ef4@mit.edu>
Date: Wed, 19 Apr 2017 13:16:25 -0400
MIME-Version: 1.0
In-Reply-To: <alpine.OSX.2.20.1704190812230.40542@darwin.oankali.net>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
[This discussion might be more appropriate for krbdev@mit.edu as it
pertains to MIT krb5 development, but I will answer here.]
On 04/19/2017 08:14 AM, Richard Silverman wrote:
> I see that there are recent pull requests on the GitHub mirror for MIT Kerberos (https://github.com/krb5/krb5). Do you prefer to receive bug reports accompanied by proposed patches there, or still in RT via krb5-bugs@mit.edu?
github is our preferred avenue for patches, while krb5-bugs@mit.edu is
still our preferred avenue for big reports. Ordinarily if you have both
in hand, it's fine to start with a github PR and we will create the bug
ticket retroactively with the commit. But in the specific case of your
recently submitted bug report (#8579), I think some careful analysis of
the bug will be required before we know the appropriate design for the
fix, so a PR might be premature.
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
