[17539] in Kerberos_V5_Development
Re: Commits to krb5-appl
daemon@ATHENA.MIT.EDU (Sam Hartman)
Wed Mar 21 17:13:35 2012
From: Sam Hartman <hartmans@mit.edu>
To: Greg Hudson <ghudson@mit.edu>
Date: Wed, 21 Mar 2012 17:13:31 -0400
In-Reply-To: <4F6954BD.3080801@mit.edu> (Greg Hudson's message of "Wed, 21 Mar
2012 00:10:37 -0400")
Message-ID: <tslobrp1wuc.fsf@mit.edu>
MIME-Version: 1.0
Cc: Russ Allbery <rra@stanford.edu>, krbdev@mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
>>>>> "Greg" == Greg Hudson <ghudson@MIT.EDU> writes:
Greg> On 03/20/2012 08:58 PM, Russ Allbery wrote:
>> It looks like I have commit access to the krb5-appl repository.
>> Should I just go ahead and commit these? If so, should I create
>> tickets for them as well, or just commit?
Greg> Yes, you can commit them. I don't think we need tickets for
Greg> changes this small. (They may get backported to the release
Greg> branch, but krb5-appl is sleepy enough that we don't need to
Greg> use the ticketing system to track backport-eligible commits.)
I kind of wonder if it's sleepy enough that a release branch does more
harm than good.
Or at least whether you want a new release branch for every point
release.
I can see possibly having a branch while stabilizing something, but it
seems like you more or less want any trunk changes since the last
release for any new release of something as low-churn as krb5-appl.
--Sam
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
