[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Epoch for node-markdown-it





On Fri, Aug 19 2022 at 05:50:46 PM +02:00:00 +02:00:00, Andrej Shadura <andrew@shadura.me> wrote:
Hi,

On Fri, 19 Aug 2022, at 17:45, Nilesh Patra wrote:
I agree, adding an epoch in this package doesn’t seem appropriate or necessary.

JTFR - Upstream released 12.0.4 in 2020, and they have reached 13.0.1
 _now_ (after two years)
 Going by previous releases, the delta between one major release is
 atleast an year.

And so reaching to 22.2.3 will take a very long time as well, if not _forever_
 and that would mean keeping up with +really for several years. I do
not think tagging this along with really is much better than adding in an epoch.
 (I personally find the former a bit more ugly for my taste)

As Jonas said, an epoch cannot be undone, +really can, regardless when this is going to happen. Both are ugly solutions, but an epoch is also evil, unlike +really 🙂

Are we going to deny every epoch request or this is going to be subjective?

I don't know if waiting potentially 10+ years for upstream to catch up is not a reasonable request, what exactly is reasonable?

In cases of reverting to an older version +really is appropriate, but with such big version difference if epoch cannot be used, why are we keeping the option of epoch at all?



Reply to: