From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-01v.sys.comcast.net (resqmta-ch2-01v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:33]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 86E6F793F1 for ; Sat, 7 Feb 2015 08:40:59 -0800 (PST) Received: from resomta-ch2-18v.sys.comcast.net ([69.252.207.114]) by resqmta-ch2-01v.sys.comcast.net with comcast id pUgp1p0052Udklx01UgqRD; Sat, 07 Feb 2015 16:40:50 +0000 Received: from eklhad ([IPv6:2601:4:5380:4ee:219:21ff:feb9:ba8d]) by resomta-ch2-18v.sys.comcast.net with comcast id pUgq1p00108MP5701UgqNe; Sat, 07 Feb 2015 16:40:50 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke User-Agent: edbrowse/3.5.3.git Date: Sat, 07 Feb 2015 11:40:49 -0500 Message-ID: <20150107114049.eklhad@comcast.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1423327250; bh=yp7sKrF/HGTunYQFJPy9U6nOWTF75MIW5C/uDGjrapE=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=YLG+Li0DijuoLb4fqCDWgQJeVi3ybEoQRTtQ7qYmC7CJjfuWESmiheO8jxHYLYqMq UtTjd+7S2NqGXNZHcIKdYmUzW5xtcde5aLbud/WCc/6piKqYrQtE0gTc5GtrF4ipru JdafIe2+8gZJ6Kc+S7ovfbrD61VK4uW5QDJlKBBnW9grunYrORKkxRLfZCq2WEJTmt PF8FHHwYTVo2QoJO9qcePRH7cvufd0wOURPrIKTXRfEvnZVHceO0awBj4kAQ23EhNx K3VUXVffJYzMkX/fply1Te2SQlwtVRhW7Q612TnJawjScwDvayiwkbKJU8V2/p3lTP Qavr+qhCxj5QQ== Subject: [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:40:59 -0000 > 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. 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. I think I'll defer to Chris on whether we should stamp version 3.5.3 now, or put some of his imap changes in first. Karl Dahlke