Rule/Change-Update-Newsletter? (was: Re: Replacing USE_GCC=any and the danfe@ filter (was: svn commit: r568012 - head/net/tightvnc))

[Matthias Andree]

Am 03.06.21 um 12:40 schrieb Torsten Zuehlsdorff:

> Without any judgment of this rule (here): i really have no idea that:
> 1) We have such a new hook
> 2) We changed the New port rule
> 
> That raises to issues directly:
> 1) I am annoyed that this was not discussed (maybe in a way i noticed?)
> 2) I am annoyed that this change was not made clear to the committer
> involved.
> 
> To address point 2: can we at least aim for a Newsletter (or a mail to
> ports-committer@) when we do such think. I really do NOT scan the
> porter-handbook for changes on a regular base (while i could also NOT
> find the change there). It would be very nice if we can be up to date to
> all relevant changes without reading through dozens of mailinglists or
> thousands of commit messages. Or has the E_NOTIME reason of most
> developer changed to E_HAVETIME? It it really a terrible idea to inform
> the team?

Such information would belong into ports/CHANGES, but we've had many
changes that are not documented there.