On Wed, Nov 20, 2019 at 12:13 PM Petr Pisar <ppi...@redhat.com> wrote:

> On 2019-11-19, John M. Harris Jr <joh...@splentity.com> wrote:
> > On Tuesday, November 19, 2019 4:42:31 AM MST Petr Pisar wrote:
> >> Manual work. Random commiters skipping them.
> >
> > If your goal is to make it so that "Random commiters" are packagers,
> that's
> > going to fall flat very quickly - as they'll just throw one version of
> the
> > package in, never think about it again. That is an untenable situation.
> >
> No. Random commiter is some one who does not know that the two
> branches have to be kept in synchronization. In other words someone else
> than the maintainer. E.g. If there is a guideline change or a SONAME
> bump then somebody touches your package.
>

While not perfect, this would be an ideal use of the README file in the
master branch.  This could specify things like, where to report bugs, if a
proven packager should try to contact the customary maintainer in advance,
if possible, how branches are maintained, etc.

regards,

bex



>
> -- Petr
> _______________________________________________
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>


-- 
Brian "bex" Exelbierd (he/him/his)
RHEL Product Management & Community Architect
@bexelbie | http://www.winglemeyer.org
bexel...@redhat.com
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Reply via email to