> Actually, I think that anybody who maintains any kind of reference to a JIRA > whether in a distribution or in their own head would like the meaning of a
> JIRA to be relatively static. I don't remember proposing to change the meaning of a JIRA with amendments. This is a separate conversation. I suppose in theory if we leave open the possibility for committers to amend a commit for a week they can do anything, but what I see with HBase anyway is amendments fix problems introduced by the change, or add missing files to fix the build. Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White) ----- Original Message ----- > From: Ted Dunning <tdunn...@maprtech.com> > To: dev@hbase.apache.org > Cc: Andrew Purtell <apurt...@apache.org> > Sent: Monday, August 15, 2011 11:45 AM > Subject: Re: Two requests from a grumpy old man > > Actually, I think that anybody who maintains any kind of reference to a JIRA > whether in a distribution or in their own head would like the meaning of a > JIRA to be relatively static. > > So even if the community doesn't explicitly know that they care about this, > I bet they care about the consequences. > > On Mon, Aug 15, 2011 at 11:36 AM, Todd Lipcon <t...@cloudera.com> wrote: > >> I understand that this is something that the community may not care >> about, since it's unique to downstream maintainers of patch series. >> But, I am guessing that other folks that maintain branches slightly >> off trunk (eg Facebook, Trend, etc) may have a similar issue with >> integrating changes into their production branches? >> >> A day may be too tight, but maybe we can compromise on a few days, or a >> week? >> >
