On Mon, Jul 17, 2023 at 9:04 AM Stefan Bethke <s...@lassitu.de> wrote:
> Hi, > > every time I submit a PR to update a port I maintain, I get conflicting > instructions about how to fill in the PR. This is really annoying, and some > committers apparently feel they will not move forward in processing the PR > unless some bureaucratic bullshit is done. > > Can the ports team please provide a concise, definitive list on how a > maintainer is supposed to fill in a port update PR, so this nonsense stops? > Hi Stefan, Having the PR database in good shape is important. It makes it more searchable and helps with consistency. The canonical information on how to properly fill a PR is in the resources found at https://www.freebsd.org/support/bugreports/ Some port specific tips would be: - If Reporter is MAINTAINER, set *maintainer-approval* attachment flag value to + (#teach) - Do not set maintainer-feedback unless to avoid maintainer timeout or if it was requested first. - - Version update: - - *Check for upstream changelog URL, add to URL field * Bugfix or security release: Set *merge-quarterly* flag to ? - * Security release: Request VuXML entry (#teach) - If port Makefile gives an error, specify target in summary, like: Fails to <target>: $error-summary Cheers. > > > Thanks, > Stefan > > -- > Stefan Bethke <s...@lassitu.de> Fon +49 151 14070811 > >
