user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: Kyle Meyer <kyle@kyleam.com>
Cc: meta@public-inbox.org
Subject: Re: release timelines (-extindex, JMAP, lei)
Date: Mon, 8 Mar 2021 02:54:59 +0000	[thread overview]
Message-ID: <20210308025459.GA23112@dcvr> (raw)
In-Reply-To: <87k0qk9lsj.fsf@kyleam.com>

Kyle Meyer <kyle@kyleam.com> wrote:
> Eric Wong writes:
> 
> > But I'm deeply worried about unleashing a new on-disk format
> > that's insufficient and being stuck supporting it forever
> > (as I am with v1 inboxes)...
> [...]
> > * lei has a bunch of rough edges and I'm not comfortable declaring
> >   it as supported, especially when there's a risk of data loss to
> >   users.
> 
> What are your thoughts on marking all things lei with a big
> experimental / subject-to-change / may-eat-your-data warning?

Yes, definitely experimental and may-eat-your-data.
I hope the subject-to-change bit can be minimized, though I'll
drop the '<>' in "lei q" JSON before release.

I'm also considering diverging from mairix in making --augment
the default behavior in "lei q".  That would make things
significantly safer, and --no-augment would be required to
clobber existing outputs.

  reply	other threads:[~2021-03-08  2:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-05 22:20 release timelines (-extindex, JMAP, lei) Eric Wong
2021-03-06 18:31 ` Kyle Meyer
2021-03-08  2:54   ` Eric Wong [this message]
2021-03-08 21:33 ` Konstantin Ryabitsev
2021-03-08 22:16   ` Eric Wong

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://public-inbox.org/README

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

  git send-email \
    --in-reply-to=20210308025459.GA23112@dcvr \
    --to=e@80x24.org \
    --cc=kyle@kyleam.com \
    --cc=meta@public-inbox.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://80x24.org/public-inbox.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).