Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 57063429E29 for ; Sat, 4 Jun 2011 07:15:50 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0.463 X-Spam-Level: X-Spam-Status: No, score=0.463 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, RDNS_DYNAMIC=0.363] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iLrbrdOegnqP for ; Sat, 4 Jun 2011 07:15:49 -0700 (PDT) Received: from xhlj.maillard.im (cha51-3-88-164-105-66.fbx.proxad.net [88.164.105.66]) by olra.theworths.org (Postfix) with ESMTP id 615ED431FB6 for ; Sat, 4 Jun 2011 07:15:49 -0700 (PDT) Received: from xhlj.maillard.im (xhlj.maillard.im [127.0.0.1]) by xhlj.maillard.im (Postfix) with ESMTP id 7CCBB2C006; Sat, 4 Jun 2011 16:15:47 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=maillard.im; h=from:to :subject:in-reply-to:references:reply-to:date:message-id :mime-version:content-type; s=postfix; bh=2j4ajdv9k0ixi7FOD+zmW2 +7juo=; b=IaAzEbCLLoKi6hpiwDsEfaMsl1nkJpU4x/dhuyUR8mijjfijqoYbKD cN00Bxn1kVxQwfyTYbJAwJppxoNterJincoegHwYg4qeALYTx92QQ6DdfKQCAdQC k6sIqZvB7jQbxGnZXGNOP+OcTQfcD3gpwx0I1IniqV77+N5LFIpxQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=maillard.im; h=from:to :subject:in-reply-to:references:reply-to:date:message-id :mime-version:content-type; q=dns; s=postfix; b=vk+JMkWVPp1D+Nwn iLs6bYX3X/bkCESHlpnvZeRLvyZthjI1yLsIuQha7a/ywdnGFdIeAz4oNAP9eKa1 75SIBdonUEveN+2HtuQXyIZN7KDXtupGo1zYVU9xExe5X7vSNOht45bhjkEEcJ53 sNsNp7DI4UuZCL7Ba1FaJzIRWho= Received: from maillard.im (unknown [192.168.0.254]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by xhlj.maillard.im (Postfix) with ESMTPSA; Sat, 4 Jun 2011 16:15:47 +0200 (CEST) From: Xavier Maillard To: David Bremner , Carl Worth , Jameson Graef Rollins , Notmuch Mail Subject: Re: When will we have our next release? In-Reply-To: <87ei39g2bn.fsf@zancas.localnet> References: <878vtile1h.fsf@yoom.home.cworth.org> <87ei39g2bn.fsf@zancas.localnet> User-Agent: Notmuch/0.5-194-gb20f9fa (http://notmuchmail.org) Emacs/23.2.1 (i486-slackware-linux-gnu) Date: Sat, 04 Jun 2011 16:27:33 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Xavier Maillard List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jun 2011 14:15:50 -0000 Hi, On Sat, 04 Jun 2011 10:21:00 -0300, David Bremner wrote: > Overall I think Carl's time based release proposal is a reasonable > plan. I think one problem we've been having is that we seem to have lost > track of > > # Releases of notmuch have a two-digit version (0.1, 0.2, etc.). We > # increment the second digit for each release and increment the first > # digit when we reach particularly major milestones of usability. > > In short, I think we are make too big of a deal out of releases. Looking > at the log between 0.5 and now, there are features enough to justify > several minor releases. Or even major ! Frankly, this project has grew up quite quickly and features are implemented at a really good rythm. The sole problem is that it is really hard to see how far we are from a release and what exactly has been cooked up since latest release (from my point of view). > On Fri, 03 Jun 2011 15:56:42 -0700, Carl Worth wrote: > > > > Frankly, I wouldn't mind doing strict time-based releases with something > > like the following: > > > > * We schedule a release period (once per month?) > > I think every two months might be a bit more comfortable, but then > again, 1 month would keep us from "making a big deal out of releases." Best before choosing the frequency is probably to try doing this a few times and be comfortable with the process. If after a few releases -i.e. say 3- the more we can do is release every trimester so do it. The process should be simple (and will be I guess) and the most difficult part is probably to document every aspect of every changes in the NEWS file (with eventually a good shaped manual ;)). > > * We schedule a "safety period" before the release (one week?) > > * At the beginning of the safety period, package up the head > > of the notmuch tree and upload to Debian experimental and > > anywhere else similar. > > Sure. I don't mind doing that part, at least for Debian. I'm going to > try to do at roughly weekly uploads to Debian experimental. Hopefully > this will get some critical mass of users testing those versions. I know it is a bit off topic here but just a question: how will you deal with dependencies ? I mean, when we need GMime vX.Y.Z and Debian has already vX.V.W ? /Xavier