From mboxrd@z Thu Jan 1 00:00:00 1970 From: Junio C Hamano Subject: Re: Plans for 2.7.1? Date: Mon, 01 Feb 2016 11:24:49 -0800 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: git@vger.kernel.org To: Johannes Schindelin X-From: git-owner@vger.kernel.org Mon Feb 01 20:25:19 2016 Return-path: Envelope-to: gcvg-git-2@plane.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aQK5v-0003x9-KK for gcvg-git-2@plane.gmane.org; Mon, 01 Feb 2016 20:25:04 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753618AbcBATYy convert rfc822-to-quoted-printable (ORCPT ); Mon, 1 Feb 2016 14:24:54 -0500 Received: from pb-smtp0.int.icgroup.com ([208.72.237.35]:55791 "EHLO sasl.smtp.pobox.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752875AbcBATYw convert rfc822-to-8bit (ORCPT ); Mon, 1 Feb 2016 14:24:52 -0500 Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-smtp0.pobox.com (Postfix) with ESMTP id 87C7B40E1C; Mon, 1 Feb 2016 14:24:51 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type:content-transfer-encoding; s=sasl; bh=2iQ8chkHKksU 5NJzxyiCSP1ZF9o=; b=rmDOmYQBUhrEQzER6k9RxQ9E4IftK504G8xBYSWpZcY6 NWfcS/NHuGARhPFLeE6QrKRadAkPBlZDh3kj8CPtwOko3mhrFCBz9d3KKyLoxeMi vlcjTwiHcUK9qyBaWniifLAfgWE9qOdzXMnwLBu+j8qYh/Ul5R+uGRD+MSAHpH0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type:content-transfer-encoding; q=dns; s=sasl; b=d80Vrz 5FbB8+LAhEdHHYt8qlEit/OQSAtiZrUdbIC3SfB1UHge6HOc4Ioq72yowiYD9mE7 kH2dTHcKqv/n+hbmpeNtSj5sXlBwjgBDzb4ry0iL6nfYyJMHbX4DgWklFP1ZwR+J zygavdzW5kk2AsNM4RBL96WIYWubF2UqInv90= Received: from pb-smtp0.int.icgroup.com (unknown [127.0.0.1]) by pb-smtp0.pobox.com (Postfix) with ESMTP id 7CF9640E1A; Mon, 1 Feb 2016 14:24:51 -0500 (EST) Received: from pobox.com (unknown [216.239.45.64]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by pb-smtp0.pobox.com (Postfix) with ESMTPSA id D59A840E19; Mon, 1 Feb 2016 14:24:50 -0500 (EST) In-Reply-To: (Johannes Schindelin's message of "Mon, 1 Feb 2016 17:54:05 +0100 (CET)") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) X-Pobox-Relay-ID: 76C8F90C-C919-11E5-92A8-04C16BB36C07-77302942!pb-smtp0.pobox.com Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: Johannes Schindelin writes: > at tinyurl.com/gitCal I see a pretty timeline regarding 2.8.0, but I = do > not see 2.7.1 planned anywhere. Yup, because maintenance releases are inherently "not planned" ;-) Unlike feature releases that are largely time-based, we cut maintenance releases only when we need to push out fixes. We do not even know in advance what breakages we would have in 2.7.0, or what fixes we would apply for them, and when these fixes would happen. > Due to signature problems (I failed to realize that SHA-1 based > .exe signatures are no longer considered valid starting from > January 1st, 2016), I got a metric ton of private and non-private > bug reports regarding "corrupt signatures", and therefore I would > like to prevent those reports from taking over my entire working > hours by simply issuing a new release of Git for Windows. > > Is 2.7.1 around the corner? Otherwise I'll just make a 2.7.0(2). Let me see what are slated for 'maint' in the current draft release notes. This actually lists what could technically be merged to 'maint'; some clean-up patches may not be worth merging down. $ Meta/ML