From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 3C355793E8 for ; Sat, 7 Feb 2015 08:24:24 -0800 (PST) Received: by mail-wi0-f177.google.com with SMTP id em10so1333517wid.4 for ; Sat, 07 Feb 2015 08:24:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=5p919ytTAT6iSlIid7mAwuaPLIlvSVgd4pIILuW35lU=; b=DqxP+w49WmVhKUHQm3IXJfeIu9ryzr+7Aag/PyWyV5HvjOYI0WGgMjUk0/oS3zuBBK h1+X24cR2Gm1R3azsha6VNk19Kao0SrsfsdfnrnV+SxdXmEGuGFa+j5K2s1ShBCyuC1X Sc2Tj/r/C7O/zISpSApdfR6aLFxveQU/sD/ozhV63kGuZAvCBs79GC7jBbfZXCDnGzOL X0DGCatpJ2JjgtXsZ7ugr02FvBXAR7E0WicBUl00ywJNvVd1THulU1SLVT2LkGv0SDMZ PnckYRYfSJLjamznJ9ZPHbXVv3WsNy/+D3BV6+qrtDBzJkDuLuw6PiGSXDYk7BwyAMMh tbJg== X-Received: by 10.194.78.231 with SMTP id e7mr20286176wjx.33.1423326254555; Sat, 07 Feb 2015 08:24:14 -0800 (PST) Received: from toaster.adamthompson.me.uk (toaster.adamthompson.me.uk. [2001:8b0:1142:9042::2]) by mx.google.com with ESMTPSA id bd8sm8198286wjc.21.2015.02.07.08.24.13 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 07 Feb 2015 08:24:13 -0800 (PST) Date: Sat, 7 Feb 2015 16:24:04 +0000 From: Adam Thompson To: Karl Dahlke Message-ID: <20150207162404.GA26357@toaster.adamthompson.me.uk> References: <20150106174819.eklhad@comcast.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7JfCtLOvnd9MIVvH" Content-Disposition: inline In-Reply-To: <20150106174819.eklhad@comcast.net> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: Edbrowse-dev@lists.the-brannons.com Subject: Re: [Edbrowse-dev] 3.5.3 X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Feb 2015 16:24:24 -0000 --7JfCtLOvnd9MIVvH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Feb 06, 2015 at 05:48:19PM -0500, Karl Dahlke wrote: > Ok I pushed a change so version is 3.5.3.git. > Chris, when the time is right, update this to 3.5.3, > mark that version in git, and then update to 3.5.4.git. > But when should that be? > When should we mark the next version? > We've made a lot of changes, good changes, since 3.5.2. > I've documented these in the CHANGES file, > please check and make sure I haven't missed anything. > Edbrowse works at least as well as before, and in many cases better, > so should we soon cut a new version 3.5.3, > or should we wait a bit and fold in the initial imap access > that Chris and I have started working on? > I would think no later than the imap push, we should mark the next version, > because some of the next changes, like Adam looking into tidy5 > to parse html, are pretty substantial and systemic. I'd say to go for the new version sooner rather than later. Additionally, if we're going for 3.5.3.git I'd propose 3.5.3.release (or some such) as a release version string. This is for a number of reasons, not least that it'll make version sorting (and version dependant package managers) behave correctly (git sorts before release in sorting) whereas 3.5.3 would probably sort *before* 3.5.3.git. This isn't a problem at the moment, but if we start publishing experimental pre-compiled packages then it will be (incidentally I'd quite like to do something like this at some stage if we don't already). I've actually seen a case (can't remember which project exactly) where package names ended up diverging from published version strings because of version sorting reasons and would rather this didn't happen to Edbrowse. It may also be interesting to think about having a head branch for development and a release branch for releases since this'd allow people to follow releases via git pull without having to worry about getting the latest unstable developments. It'd also enable us to work on new features and cut a new release at the same time. Cheers, Adam. --7JfCtLOvnd9MIVvH Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJU1jwkAAoJELZ22lNQBzHO+tUH/26LvgS1eoxzKoUZ92s1ab/+ KW3F897V+8KT2YVhTQlf3GbNpYRIz3H3KYB1OHjZfGbHvRMpMUnAUrisLd7/E0fS ng/InyHBQ9dajO853RdxkO8ofJW1aOpg1jz4ORslzDl0KdaZEwEhHHnezFMftQ4j 8mw24wq1xl5cKm3jE2q+TgzadOFuy1mu7t7tyLx22NysSFlBC/0C0lBKMntY0VcP 1oXCx+uZgAclTqVZ83BlyTlq/83nX1xKBpzPtJefY+Khuzc0rNL9cDuqxGsT9MNl 3z9NFRvF5bejdI7v/GUEK9ZeJ883/1KPMz2mKkbxui6uU73sEnTdTigTZgTmDZo= =cMfx -----END PGP SIGNATURE----- --7JfCtLOvnd9MIVvH--