From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 9DF0A79066 for ; Sat, 7 Feb 2015 10:07:17 -0800 (PST) Received: by mail-wi0-f173.google.com with SMTP id em10so1677701wid.0 for ; Sat, 07 Feb 2015 10:07:08 -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=qTfBp8uuZExXfB9dSEn8zCjwJP6g65HqlTw7is6Shj8=; b=yeBUqgkmSnbyccA5efUiz2sgE56a+vbSpwu1h+TJcSWFRJt1gy2xlbCptH8W5jKpnZ Gi6hSgLx/qHW1HDGyQrlL0CHXIHj5eiSf5hVFY2vjFSuKMn1E+3zIsuVMkR0vmW7qeq5 CN+Dfl/N/VKkvYiI/voKI2u+053i8aQ77tQFlr7zPBKPsL7+B/URrRoZ+hRdA+fJylBp 08kg6cauBcBtKAC8JG3exwFXNG0G82zVo4ZYzuoxOaOFPvdOtaRWIoHQgT6/E+jdbjnZ AxeG4IqwRkq6+O9L59RK2pq8IEn/sZ0Bv49P1PxhM1jSvaczDD+1/HhW+OYstcn2WlAI RITQ== X-Received: by 10.180.100.104 with SMTP id ex8mr16671838wib.57.1423332427858; Sat, 07 Feb 2015 10:07:07 -0800 (PST) Received: from toaster.adamthompson.me.uk (toaster.adamthompson.me.uk. [2001:8b0:1142:9042::2]) by mx.google.com with ESMTPSA id g10sm6620191wic.7.2015.02.07.10.07.06 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 07 Feb 2015 10:07:06 -0800 (PST) Date: Sat, 7 Feb 2015 18:07:04 +0000 From: Adam Thompson To: Karl Dahlke Message-ID: <20150207180704.GB26357@toaster.adamthompson.me.uk> References: <20150107114049.eklhad@comcast.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="QKdGvSO+nmPlgiQ/" Content-Disposition: inline In-Reply-To: <20150107114049.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 18:07:18 -0000 --QKdGvSO+nmPlgiQ/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Feb 07, 2015 at 11:40:49AM -0500, Karl Dahlke wrote: > > It may also be interesting to think about having a head branch for deve= lopment > > and a release branch for releases since this'd allow people to follow r= eleases > > via git pull without having to worry about getting the latest unstable = developments. >=20 > Well perhaps - but I'm trying to avoid git version complexity > and branches and the like. > The few intrepid folks who follow the latest often want the latest, > even that last bug or feature that we just fixed, > and they are sometimes helpful in finding more bugs, so we can fix them > *before* any release or version cuts over. > Recall when a user found a seg fault just last month and I fixed it, > and didn't that happen a month before too? > These are our beta testers, and I think they > really do want the latest, and we want them to have the latest. > It's a win win. > Besides, our "unstable" snapshots aren't really that unstable. > We are reasonably careful in what we push. So if they want the latest they track head. This is very simple in git. If they want the release branch (with bug fixes) they track release. This enables us to do bug fix releases whilst getting on with major develop= ments. For example, currently we're debating whether to release 3.5.3, but also talking about looking at tidy5 based html parsing and all the chan= ges that implies. If there's a bug in 3.5.3 which we don't find, but users do after the relea= se, we'll need a way to fix that, however we can't hold off the tidy5 (or other parsing lib) changes indefinitely (well we can but not if we want to make progress). This hasn't been an issue before due to the incremental nature of changes, however for less incremental changes this will become an issue fairly quick= ly I suspect. Cheers, Adam. --QKdGvSO+nmPlgiQ/ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJU1lRIAAoJELZ22lNQBzHOdJoH/RnGxeOzL758UvxYNxUKgNLw I82SoW+WCLwXRB4pTV7Uux7boUxnAwdr9EoxDz4KDcrqDxpe4ZpfPpat1DsZTY7m jTLmwtwsuNK0cgWPXfF/Pa4HG9iaMjbRvBBkv/sJ7WB8weIxWHRz3njZBSyx+PHl o13dpP3q+LXjiK5n4tONHc+BoxLMzsxQILAK9/Ul2J/3tkeWllaan42/vzs82d0y FIL4WRvkEKy0yZXLobfcIPQoFdnFT9KLgZp5stfjlD7dF8PACrQLUiu0uirp9u99 L14MQXo0uKPjtRtGJBsC9V55pfbEAzTQLmPCo+PZDeKkWIxLjyzoqmiwVCzasFo= =AZtf -----END PGP SIGNATURE----- --QKdGvSO+nmPlgiQ/--