unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Xavier Maillard <xavier@maillard.im>
To: David Bremner <bremner@unb.ca>, Carl Worth <cworth@cworth.org>,
	Jameson Graef Rollins <jrollins@finestructure.net>,
	Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: When will we have our next release?
Date: Sat, 04 Jun 2011 16:27:33 +0200	[thread overview]
Message-ID: <m262olekoa.fsf@gnu.org> (raw)
In-Reply-To: <87ei39g2bn.fsf@zancas.localnet>

Hi,

On Sat, 04 Jun 2011 10:21:00 -0300, David Bremner <bremner@unb.ca> 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 <cworth@cworth.org> 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

  reply	other threads:[~2011-06-04 14:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-03 22:56 When will we have our next release? Carl Worth
2011-06-04 13:21 ` David Bremner
2011-06-04 14:27   ` Xavier Maillard [this message]
2011-06-04 18:50     ` David Bremner
2011-06-04 14:19 ` Xavier Maillard
2011-06-07 16:44 ` Jameson Graef Rollins
2011-06-07 19:15   ` Sebastian Spaeth
2011-06-23  1:21   ` Carl Worth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m262olekoa.fsf@gnu.org \
    --to=xavier@maillard.im \
    --cc=bremner@unb.ca \
    --cc=cworth@cworth.org \
    --cc=jrollins@finestructure.net \
    --cc=notmuch@notmuchmail.org \
    --cc=xma@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).