Need everyone helping out with the bug queue

Jeff Schroeder jeffschroed at gmail.com
Sun Dec 25 14:53:14 UTC 2011


FYI in a github pull request, put in the description something like:
Fixes #138

Where 138 is an issue number. That will link the two together and as soon as the pull request is merged, the bug will auto-close. As a developer / co-maintainer of the salt stack project (http://github.com/saltstack/salt or http://saltstack.org), we do that a lot.

Sent from my iPhone

On Dec 25, 2011, at 4:21, Jörgen Maas <jorgen.maas at gmail.com> wrote:

> On Sat, Dec 24, 2011 at 10:49 PM, Michael DeHaan
> <michael.dehaan at gmail.com> wrote:
>> 
>> (3)  Fix bugs and send in pull requests, and close bug tickets that are user
>> error with explanations of what the users should be doing.   Help keep the
>> bug queue extra small and the master branch very high quality.   If you're
>> submitting a feature or a bug fix for something that affects you, also try
>> to fix some bugs that don't affect you.   If you are submitting a bug, see
>> if you can also accompany that bug report with a fix.
> 
> I agree, can you please give me the authorization to close bugs?
> E.g. #23 for which i sent a pull request, it got merged but the bug remains open
> 
> Thanks!
> -- 
> Grtz,
> Jörgen Maas
> _______________________________________________
> cobbler-devel mailing list
> cobbler-devel at lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/cobbler-devel


More information about the cobbler mailing list