From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dani Moncayo Newsgroups: gmane.emacs.devel Subject: Emacs versioning scheme Date: Wed, 22 Aug 2012 09:29:15 +0200 Message-ID: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-Trace: ger.gmane.org 1345620567 23532 80.91.229.3 (22 Aug 2012 07:29:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 22 Aug 2012 07:29:27 +0000 (UTC) To: Emacs development discussions Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Aug 22 09:29:27 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1T45NU-0003zd-OG for ged-emacs-devel@m.gmane.org; Wed, 22 Aug 2012 09:29:24 +0200 Original-Received: from localhost ([::1]:47711 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T45NS-0001sO-UY for ged-emacs-devel@m.gmane.org; Wed, 22 Aug 2012 03:29:22 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:48777) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T45NR-0001sF-4o for emacs-devel@gnu.org; Wed, 22 Aug 2012 03:29:21 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1T45NM-0007kx-4E for emacs-devel@gnu.org; Wed, 22 Aug 2012 03:29:20 -0400 Original-Received: from mail-ob0-f169.google.com ([209.85.214.169]:36963) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T45NL-0007kt-VP for emacs-devel@gnu.org; Wed, 22 Aug 2012 03:29:16 -0400 Original-Received: by obhx4 with SMTP id x4so1155485obh.0 for ; Wed, 22 Aug 2012 00:29:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=BvgrJrpvOJmvw/Com3sDg8bRZ9FfrOcDjf6CSsZgL7M=; b=Z1M0/SgmPk8SzoSZNQXtX+02RG5TwNNjtjeryCNbpz1rZKW2ikFbFAwpkvBoPhDC1N rjJQiqlRRrNJtMpOWhDSqYCPIs0BJB8RjThIOpdraGunGafP6pmZwQvWcmoeMIwQ03+o grHwWD6TW7oBUZZJT5MisDYuG52R763IVJcZsTGwAjl89c83voVJ98cPw8OI4wQLUnb/ nohIxl6FjnEQSkA9E4kq3DyLxDakw3Xm+5l+u+LuyetoIDEgse8/NW/M1+7Y4lIoNYVN m8dXWNjxgatWEXj5IGpzTJJjtvUrqm4SOTPWvqA0bUc07ymlVyUvpKQdgQq7RAZ6dbp2 08Vw== Original-Received: by 10.60.3.194 with SMTP id e2mr14781338oee.1.1345620555341; Wed, 22 Aug 2012 00:29:15 -0700 (PDT) Original-Received: by 10.60.79.226 with HTTP; Wed, 22 Aug 2012 00:29:15 -0700 (PDT) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 209.85.214.169 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:152733 Archived-At: Hello, One question: Currently, some patches commited to trunk are being tagged as "version: 24.3". But if some other severe bug arises upon the (not yet) released Emacs 24.2, so that a 24.3 release becomes necessary (from the emacs-24 branch), then such tags will be incorrect, won't they? It seems that the current versioning pattern has this problem. We don't know beforehand the version under which the current trunk code will be released. So, what about switching to a different pattern which doesn't have this problem? For example: Name the next trunk's branch as "emacs-24.3", and every release made from that branch would be labeled "emacs 24.3.x". This way, we would know for sure that the trunk code would be released as version "24.4" (or "25.1" -- what the maintainer's decide). -- Dani Moncayo