Attempting to switch to asciidoctor has resulted in several issues including a 
greater difficulty in keeping the builds reproducible (date insertion issues). 
In addition I am not fan of the asciidoctor style and bringing in asciidoc's 
directly would result in license contamination. Since asciidoc is no longer EOL 
with the release of a py3 version which should require no changes to 
autorevision, I would rather stick with that.

On Tue, 3 Apr 2018 04:14:58 -0700 Joseph Herlant <herla...@gmail.com> wrote:
> Package: autorevision
> Version: 1.21-1
> Severity: wishlist
> 
> Dear Maintainer,
> 
> Asciidoc is currently facing its end of life and I'm working with the 
> different
> packages that depend on it to get its EOL go smooth.
> 
> There are several alternatives to asciidoc like asciidoctor for
> example (which is the replacement recommended by asciidoc developers).
> 
> Could you have your package migrated to an alternative system please?
> 
> Thanks for your help,
> Joseph
> 
> 

Attachment: signature.asc
Description: Message signed with OpenPGP

Reply via email to