"Perhaps the best thing to do is to file a companion bug, and raise the priority of that bug to "major" whenever a patch is available, to trigger a review."
How do you let many first time people this? On Mon, Sep 22, 2014 at 2:50 PM, Miguel de Icaza <mig...@xamarin.com> wrote: > >> Tru dat. However, when broken stuff doesn't get fixed, it drives users >> away. I'll cite myself as an example: We've had a pull request >> outstanding since April https://github.com/mono/mono/pull/1004, prior to >> which, SslStream is simply unusable (mono SslStream server is incompatible >> with mono SslStream client). > > > This is a side effect of us getting lazy. > > We used GitHub's "assign" feature, to assign this contribution to be > reviewed by someone. > > But the fact that GitHub has the feature does not mean that we have made > it a part of our process to review those contributions. In general, GitHub > produces too much noise, and I know of too many people that just filter > those notifications to a folder that goes unattended for years. > > Perhaps the best thing to do is to file a companion bug, and raise the > priority of that bug to "major" whenever a patch is available, to trigger a > review. > > Miguel > > _______________________________________________ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list > > -- Studying for the Turing test
_______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list