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