Community mailing list archives

community@mail.odoo.com

Re: The issue mountain on github

by
Antony Lesuisse (al)
- 07/28/2015 20:00:42
The solution is to create pull request telling the issue AND providing the 
fix. Or to quote linus 'Talk is cheap. Show me the code.' :)

PLEASE dont create both an issue and a PR, if you have a patch only create a 
pr explaining the issue and providing the fix. It's explained here 
https://github.com/odoo/odoo/wiki/Contributing

We mainly process PRs and moslty not issues (unless its a security problem).

In 1 year we processed 2516 PRs and there are still currently 438 PR to 
process (please use the filter from the wiki to get the accurate number).

https://github.com/odoo/odoo/wiki


On 07/29/2015 12:08 AM, Nicolas Schmitt wrote:
> Hi guys,
>
> burrying up a rather old issue, but I have not understood clearly Odoo
> S.A. position on this topic.
>
> The problem is rather easy: every week appear more issues than are tacled,
> and many important ones are rotting in the GitHub.
> It seems that as of now, 1 641 are not assigned, meaning their severity
> has not been evaluated.
>
> Would you happen to have found some kind of solution, or something like
> that?
>
> Moreover, when the version 9 will be released, I would expect a sharp
> increase in issues...
>
> Thanks
>
> On 09/07/15, Carlos Liébana wrote:
>> Troll ;)
>> 2015-07-09 12:18 GMT+02:00 Graeme Gellatly < gdgellatly@gmail.com [1] > :
>> There is a code hosting site called launchpad which has great issue management and access control. I used it before for an open source ERP.
>> it also supports git now.
>> Sent from TypeMail [2]
>> On 9 Jul 2015, at 9:28 PM, Martin Trigaux < mat@odoo.com [3] > wrote:
>> On 08/07/15 15:47, Alan Bell wrote:
>> > https://help.github.com/articles/issues-only-access-permissions/ [4]
>> >
>> > presumably this could be done with a read only main repository and a more open issues repository rather than requiring a private repository for the code hosting. I am not entirely convinced by this approach to be honest, waiting for the better permissions to be implemented might be best
>> >
>> That may work for issues only but not for pull requests. And as you, I
>> am not convinced it's the right way to process. Duplicating repositories
>> is making harder to link issues and commits (e.g. using "Fix #42" in
>> commit message)
>> --
>> Martin Trigaux
>> Odoo (Formerly OpenERP)
>> https://odoo.com [5]
>> https://github.com/mart-e [6]
>> _______________________________________________
>> Mailing-List: https://www.odoo.com/groups/community-59 [7]
>> Post to: mailto: community@mail.odoo.com [8]
>> Unsubscribe: https://www.odoo.com/groups?unsubscribe [9]
>>
>> _______________________________________________
>> Mailing-List: https://www.odoo.com/groups/community-59 [10]
>> Post to: mailto: community@mail.odoo.com [11]
>> Unsubscribe: https://www.odoo.com/groups?unsubscribe [12]
>>
>>
>> --
>> --------------------------
>>
>> * CARLOS LIÉBANA ANERO *
>> Director | factorlibre.com [13]
>> +34 635 86 67 92
>> @carlosliebana
>>
>> _______________________________________________
>> Mailing-List: https://www.odoo.com/groups/community-59
>> Post to: mailto:community@mail.odoo.com
>> Unsubscribe: https://www.odoo.com/groups?unsubscribe
>>
>>
>>
>> [1] mailto:gdgellatly@gmail.com
>> [2] http://www.typeapp.com/r
>> [3] mailto:mat@odoo.com
>> [4] https://help.github.com/articles/issues-only-access-permissions/
>> [5] https://odoo.com
>> [6] https://github.com/mart-e
>> [7] https://www.odoo.com/groups/community-59
>> [8] mailto:community@mail.odoo.com
>> [9] https://www.odoo.com/groups?unsubscribe
>> [10] https://www.odoo.com/groups/community-59
>> [11] mailto:community@mail.odoo.com
>> [12] https://www.odoo.com/groups?unsubscribe
>> [13] http://factorlibre.com
>
> _______________________________________________
> Mailing-List: https://www.odoo.com/groups/community-59
> Post to: mailto:community@mail.odoo.com
> Unsubscribe: https://www.odoo.com/groups?unsubscribe
>