user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <>
Subject: [ANNOUNCE] public-inbox 1.0.0
Date: Thu, 8 Feb 2018 02:33:57 +0000	[thread overview]
Message-ID: <> (raw)

After some 3.5 odd years of working on this, I suppose now is
as good a time as any to tar this up and call it 1.0.0.

The TODO list is still very long and there'll be some new
development in coming weeks :>

So, here you have a release:

Checksums, mainly as a safeguard against accidental file corruption:

SHA-256 4a08569f3d99310f713bb32bec0aa4819d6b41871e0421ec4eec0657a5582216
	(in other words, don't trust me; instead read the code :>)

                 reply	other threads:[~2018-02-08  2:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

  List information:

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

  git send-email \ \ \ \
    --subject='Re: [ANNOUNCE] public-inbox 1.0.0' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:

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).