discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: discuss@mdocml.bsd.lv
Subject: mandoc 1.13.x end of life
Date: Sun, 2 Apr 2017 14:57:40 +0200	[thread overview]
Message-ID: <20170402125740.GB79932@athene.usta.de> (raw)

Hi,

i'm officially declaring the mandoc-1.13 branch obsolete.
There was no feedback whatsoever regarding the 1.13.5 release
candidate, and FreeBSD-stable made the explicit decision to migrate
to mandoc-1.14 (thanks to Baptiste Daroussin for volunteering to
move that project forward).  So given the lack of interest, maintaining
the 1.13 branch would seem like a waste of time.

All systems still using mandoc-1.13.4 or even older releases
are encouraged to upgrade to mandoc-1.14.1.


Regarding the mid-term future of mandoc, i'm likely to

 - continue the parser reorganization, making even better
   low level roff(7) support possible in the long term
 - strengthen the four-layer architecture (parsers, state engines,
   validators, formatters) by moving duplicate code from the
   formatters to the state engines, and maybe some additional
   bits to the validators
 - unify the hash tables
 - maybe simplify some data structures
 - probably start making some invariants explicit
 - improve regression test coverage

So for some time, the focus is likely to be on code quality
rather than on features.  Of course that doesn't exclude closing
feature gaps when important ones are found.

Yours,
  Ingo
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

                 reply	other threads:[~2017-04-02 12:57 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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=20170402125740.GB79932@athene.usta.de \
    --to=schwarze@usta.de \
    --cc=discuss@mdocml.bsd.lv \
    /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.
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 NNTP newsgroup(s).