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

Re: Epoch for node-markdown-it





On വെ, ഓഗ 19, 2022 at 6:00 വൈകു, Simon McVittie <smcv@debian.org> wrote:
On Fri, 19 Aug 2022 at 21:36:24 +0530, Pirate Praveen wrote:
Are we going to deny every epoch request or this is going to be subjective?

If there was a correct objective rule for what to do, we'd be applying
that rule mechanically, not asking our fellow developers for advice.
Epochs cause problems, but sometimes the alternatives are worse. Deciding which is the least-bad option is inherently a subjective question and you
are not going to get an objective answer to it.


I think we can document the most commonly occuring cases and their pros and cons for the epoch, only if something is not covered by the common case we should ask in -devel. Current way of long thread on -devel for every epoch bump is too much demotivating and time draining for very little benefit. People just repeat the same boilerplate arguments without even looking at the specifics of the case most of the time. Is the opinions on -devel binding? What if when conflicting opinions are there? For example I'm convinced we need an epoch here, there are people who objected, can I still go ahead and upload with epoch?

I do not have a strong opinion either way on this particular situation
without knowing where 22.2.3 came from. As a way to mitigate this sort
of thing in future, I'd suggest that maintainers/sponsors should confirm
whether upstreams were intentionally doing a multi-version jump like
that one before uploading the new version.


I don't think this is going to be foolproof.
    smcv




Reply to: