Re: Closing the merge window for 1.6.0
From: Dmitry Potapov <hidden>
Date: 2016-06-15 22:44:57
On Tue, Jul 15, 2008 at 04:27:02PM +0100, Johannes Schindelin wrote:
quoted
From the time balance sheet, it does not look good at all: a few minutesfor Junio to change and commit, up to a few hours (because they missed it in the release notes) for probably more than hundred repository maintainers that are not subscribed to the Git mailing list.
If you just grab sources and never read release notes, there is nothing that can help you. If Git 1.6.0 is not the right moment to do these changes then Git 1.6.1 is neither, regardless whether Debian will release Lenny by that time or not. People do not upgrade their distro in the day of release. Some upgraded to Etch not so long ago. So, should we wait for another year till 1.7.0?
And I absolutely agree with Pasky that this does _nothing_ in the vague direction of wielding a reputation of being easy to use.
I don't think Git 1.4 is easy to use. If you want Git that is easy to use install Git 1.5.x. And, it is *much* easier to install Git from backports then to deal with usability issues of Git 1.4 and the lack of community support. So, I don't see how this change may hurt.
Sure, we can make it easy on ourselves. And it is just as easy to make it hard on others. If you're okay with that, I am not.
It has *nothing* to do with making easy on ourselves and hard on others. The question here is what is the appropriate time to change these default settings, and I believe that *major* releases are the appropriate time while minor ones are not. Dmitry