Date: Mon, 17 Jul 2023 09:22:55 +0200 From: =?UTF-8?Q?Fernando_Apestegu=C3=ADa?= <fernando.apesteguia@gmail.com> To: Stefan Bethke <stb@lassitu.de> Cc: ports@freebsd.org Subject: Re: Can someone please post a concise list of things maintainers are supposed to do? Message-ID: <CAGwOe2bzoGNGXNdF7EObACN5ynszTWgFxvhQaAk6qLQhjtL_GQ@mail.gmail.com> In-Reply-To: <6D24E23B-1F79-47E9-B533-361188502BEA@lassitu.de> References: <6D24E23B-1F79-47E9-B533-361188502BEA@lassitu.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000965bfc0600a9ab39 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Jul 17, 2023 at 9:04=E2=80=AFAM Stefan Bethke <stb@lassitu.de> wrot= e: > 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 so= me > committers apparently feel they will not move forward in processing the P= R > 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 stop= s? > 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 <stb@lassitu.de> Fon +49 151 14070811 > > --000000000000965bfc0600a9ab39 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">= <div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jul 17, 2023 at 9:04=E2=80=AF= AM Stefan Bethke <<a href=3D"mailto:stb@lassitu.de">stb@lassitu.de</a>&g= t; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p= x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br= > <br> every time I submit a PR to update a port I maintain, I get conflicting ins= tructions about how to fill in the PR. This is really annoying, and some co= mmitters apparently feel they will not move forward in processing the PR un= less some bureaucratic bullshit is done.<br> <br> Can the ports team please provide a concise, definitive list on how a maint= ainer is supposed to fill in a port update PR, so this nonsense stops?<br><= /blockquote><div><br></div><div>Hi Stefan,<br></div><div><br></div><div>Hav= ing the PR database in good shape is important. It makes it more searchable= and helps with consistency.<br></div><div><br></div><div>The canonical inf= ormation on how to properly fill a PR is in the resources found at <a href= =3D"https://www.freebsd.org/support/bugreports/">https://www.freebsd.org/su= pport/bugreports/</a></div><div><br></div><div>Some port specific tips woul= d be:<br></div><div><li><p class=3D"gmail-line862">If Reporter is MAINTAINE= R, set <em>maintainer-approval</em> attachment flag value to + (#teach) <br= ></p></li><li>Do not set maintainer-feedback unless to avoid maintainer tim= eout or if it was requested first.</li><li><br></li><li>Version update: <sp= an class=3D"gmail-anchor" id=3D"gmail-line-212"></span></li><li><br></li><l= i>=C2=A0*Check for upstream changelog URL, add to URL field <span class=3D"= gmail-anchor" id=3D"gmail-line-213"></span><p class=3D"gmail-line862">=C2= =A0* Bugfix or security release: Set <em>merge-quarterly</em> flag to ? <sp= an class=3D"gmail-anchor" id=3D"gmail-line-214"></span></p></li><li><p clas= s=3D"gmail-line862">=C2=A0* Security release: Request VuXML entry (#teach) = <span class=3D"gmail-anchor" id=3D"gmail-line-215"></span></p></li><li><p c= lass=3D"gmail-line862">If port Makefile gives an error, specify target in s= ummary, like: Fails to <target>: $error-summary <span class=3D"gmail-= anchor" id=3D"gmail-line-216"></span></p></li></div><div></div><div>Cheers.= <br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.= 8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <br> <br> Thanks,<br> Stefan<br> <br> --<br> Stefan Bethke <<a href=3D"mailto:stb@lassitu.de" target=3D"_blank">stb@l= assitu.de</a>>=C2=A0 =C2=A0Fon +49 151 14070811<br> <br> </blockquote></div></div> --000000000000965bfc0600a9ab39--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGwOe2bzoGNGXNdF7EObACN5ynszTWgFxvhQaAk6qLQhjtL_GQ>