Date: Sat, 23 Aug 2014 18:59:45 -0400
From: Austin Clements <amdragon@MIT.EDU>
To: Jani Nikula <jani@nikula.org>
Subject: Re: [PATCH v3 03/13] new: Don't report version after upgrade
Message-ID: <20140823225945.GL3015@mit.edu>
References: <1406859003-11561-1-git-send-email-amdragon@mit.edu>
	<1406859003-11561-4-git-send-email-amdragon@mit.edu>
	<87siknjjvm.fsf@nikula.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87siknjjvm.fsf@nikula.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: notmuch@notmuchmail.org
Precedence: list

Quoth Jani Nikula on Aug 23 at  6:39 pm:
> On Fri, 01 Aug 2014, Austin Clements <amdragon@MIT.EDU> wrote:
> > The version number has always been pretty meaningless to the user and
> > it's about to become even more meaningless with the introduction of
> > "features".  Hopefully, the database will remain on version 3 for some
> > time to come; however, the introduction of new features over time in
> > version 3 will necessitate upgrades within version 3.  It would be
> > confusing if we always tell the user they've been "upgraded to version
> > 3".  If the user wants to know what's new, they should read the news.
> 
> I think this is good for now.
> 
> What do you think about adding notmuch_database_get_features(), and
> printing that?

Mark had a similar comment, so here's my reply:
id:20140727162426.GF13893@mit.edu

I'm happy with adding more transparency around this, though I'd prefer
to do it as follow-up to avoid expanding this series and because I'm
pretty sure adding something like notmuch_database_get_features
wouldn't require any non-trivial changes to the stuff in this series.

> BR,
> Jani.