Community mailing list archives

community@mail.odoo.com

Re: The issue mountain on github

by
Antony Lesuisse (al)
- 07/29/2015 16:30:42
Sometimes an issue is reported by a non developer then afterwards someone else 
create a fix for that issue. If someone wants to learn odoo quickly i 
encourage them to try to tackle issues it's a very effective way to become 
proficient with the odoo code base.

So it's not useless to report issue but you should be aware than they are 
processed with a lower priority. I hope that explaining this policy will avoid 
all frustrations among issue reporters.

On 07/29/2015 10:08 PM, Nicolas Schmitt wrote:
> Well, even though they will maybe never handle/fix it, I think that we
> should still create issues, because when someone else stumbles on the
> same thing, having a bug report helps to share information, thoughts,
> etc, even though Odoo S.A. may not take part in the process.
>
> On 29/07/15, OpenERP Master wrote:
>> That is basically saying there really isn't a bug reporting system unless you provide a fix or it is a critical issue in which case you probably already know about it.
>> I stopped reporting anything because they did not receive any response
>> On Wed, Jul 29, 2015 at 1:47 PM, Antony Lesuisse < al@openerp.com [1] > wrote:
>> We sometimes look at issues but we give a much higher priority to pull request
>> because it means somebody spent some time hunting for the cause of the problem
>> and figuring a possible solution.
>> Odoo enteprise customers may open tickets for bug they encounter on databases
>> covered by their contract and the odoo enterprise team will quickly
>> investigate it and fix it if it's a bug (usually the same day sometime it
>> takes more time when the issue is complex).
>> It's the same team that process github issues and pull request so the priority
>> is Enterprise customer tickets, then pull requests then github issues on a
>> best effort basis.
>> Of course when an issue is serious, ignoring whoever submitted it, we look at
>> it promptly.
>> On 07/29/2015 07:18 PM, Eva Pinter @ xpansa wrote:
>> > Hi Antony,
>> >
>> >
>> > I totally understand that everyone can contribute to the improvement of Odoo,
>> > but if you want also to have functional people (like me, I do not write a line
>> > of code) checking the system and reporting issues, you may also want to check
>> > what these people have to say.
>> >
>> > So, I do not believe that asking for a solution from everyone is the way to
>> > go. There must be a better way.
>> >
>> > Regards
>> > --
>> >
>> > Best Regards,
>> > Eva Pinter
>> >
>> > Sales and Marketing Director,XPANSA Logistics | ERP, BI, E-commerce, Data
>> > Mining and DMS consulting
>> > *Xpansa CLOUD | Full Business IT Infrastructure |*
>> > https://xpansa.com/products/xpansa-odoo-alfresco-bi-saas/ [2]
>> > *mERP |** Odoo Android App | *_ merpapp.com [3] _
>> >
>> > /// site : xpansa.com [4]
>> > /// mail : eva.pinter@xpansa.com [5] <mailto: roman.gurinovich@xpansa.com [6] >
>> > /// phone, IE : +44 (0)7596 40 30 99
>> > /// skype : epinter
>> >
>> >> On 29 Jul 2015, at 01:02, Antony Lesuisse < al@openerp.com [7]
>> >> <mailto: al@openerp.com [8] >> wrote:
>> >>
>> >> 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 [9]
>> >>
>> >> 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 [10]
>> >>
>> >>
>> >> 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 :
>> >> >> 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 wrote:
>> >> >> On 08/07/15 15:47, Alan Bell wrote:
>> >> >> > https://help.github.com/articles/issues-only-access-permissions/ [11]  [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 [12]  [5]
>> >> >> https://github.com/mart-e [13]  [6]
>> >> >> _______________________________________________
>> >> >> Mailing-List: https://www.odoo.com/groups/community-59 [14]  [7]
>> >> >> Post to: mailto: community@mail.odoo.com [15]  <mailto: community@mail.odoo.com [16] > [8]
>> >> >> Unsubscribe: https://www.odoo.com/groups?unsubscribe [17]  [9]
>> >> >>
>> >> >> _______________________________________________
>> >> >> Mailing-List: https://www.odoo.com/groups/community-59 [18]  [10]
>> >> >> Post to: mailto: community@mail.odoo.com [19]  <mailto: community@mail.odoo.com [20] > [11]
>> >> >> Unsubscribe: https://www.odoo.com/groups?unsubscribe [21]  [12]
>> >> >>
>> >> >>
>> >> >> --
>> >> >> --------------------------
>> >> >>
>> >> >> * CARLOS LIÉBANA ANERO *
>> >> >> Director | factorlibre.com [22]   [13]
>> >> >> +34 635 86 67 92 [23]
>> >> >> @carlosliebana
>> >> >>
>> >> >> _______________________________________________
>> >> >> Mailing-List: https://www.odoo.com/groups/community-59 [24]
>> >> >> Post to:mailto: community@mail.odoo.com [25]
>> >> >> Unsubscribe: https://www.odoo.com/groups?unsubscribe [26]
>> >> >>
>> >> >>
>> >> >>
>> >> >> [1]mailto: gdgellatly@gmail.com [27]
>> >> >> [2] http://www.typeapp.com/r [28]
>> >> >> [3]mailto: mat@odoo.com [29]
>> >> >> [4] https://help.github.com/articles/issues-only-access-permissions/ [30]
>> >> >> [5] https://odoo.com [31]
>> >> >> [6] https://github.com/mart-e [32]
>> >> >> [7] https://www.odoo.com/groups/community-59 [33]
>> >> >> [8]mailto: community@mail.odoo.com [34]
>> >> >> [9] https://www.odoo.com/groups?unsubscribe [35]
>> >> >> [10] https://www.odoo.com/groups/community-59 [36]
>> >> >> [11]mailto: community@mail.odoo.com [37]
>> >> >> [12] https://www.odoo.com/groups?unsubscribe [38]
>> >> >> [13] http://factorlibre.com [39]
>> >> >
>> >> > _______________________________________________
>> >> > Mailing-List: https://www.odoo.com/groups/community-59 [40]
>> >> > Post to:mailto: community@mail.odoo.com [41]
>> >> > Unsubscribe: https://www.odoo.com/groups?unsubscribe [42]
>> >> >
>> >>
>> >> _______________________________________________
>> >> Mailing-List: https://www.odoo.com/groups/community-59 [43]
>> >> Post to: mailto: community@mail.odoo.com [44]
>> >> Unsubscribe: https://www.odoo.com/groups?unsubscribe [45]
>> >>
>> >
>> > _______________________________________________
>> > Mailing-List: https://www.odoo.com/groups/community-59 [46]
>> > Post to: mailto: community@mail.odoo.com [47]
>> > Unsubscribe: https://www.odoo.com/groups?unsubscribe [48]
>> >
>> _______________________________________________
>> Mailing-List: https://www.odoo.com/groups/community-59 [49]
>> Post to: mailto: community@mail.odoo.com [50]
>> Unsubscribe: https://www.odoo.com/groups?unsubscribe [51]
>>
>>
>> _______________________________________________
>> 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:al@openerp.com
>> [2] https://xpansa.com/products/xpansa-odoo-alfresco-bi-saas/
>> [3] http://merpapp.com
>> [4] http://xpansa.com
>> [5] mailto:eva.pinter@xpansa.com
>> [6] mailto:roman.gurinovich@xpansa.com
>> [7] mailto:al@openerp.com
>> [8] mailto:al@openerp.com
>> [9] https://github.com/odoo/odoo/wiki/Contributing
>> [10] https://github.com/odoo/odoo/wiki
>> [11] https://help.github.com/articles/issues-only-access-permissions/
>> [12] https://odoo.com
>> [13] https://github.com/mart-e
>> [14] https://www.odoo.com/groups/community-59
>> [15] mailto:community@mail.odoo.com
>> [16] mailto:community@mail.odoo.com
>> [17] https://www.odoo.com/groups?unsubscribe
>> [18] https://www.odoo.com/groups/community-59
>> [19] mailto:community@mail.odoo.com
>> [20] mailto:community@mail.odoo.com
>> [21] https://www.odoo.com/groups?unsubscribe
>> [22] http://factorlibre.com
>> [23] tel:%2B34 635 86 67 92
>> [24] https://www.odoo.com/groups/community-59
>> [25] mailto:community@mail.odoo.com
>> [26] https://www.odoo.com/groups?unsubscribe
>> [27] mailto:gdgellatly@gmail.com
>> [28] http://www.typeapp.com/r
>> [29] mailto:mat@odoo.com
>> [30] https://help.github.com/articles/issues-only-access-permissions/
>> [31] https://odoo.com
>> [32] https://github.com/mart-e
>> [33] https://www.odoo.com/groups/community-59
>> [34] mailto:community@mail.odoo.com
>> [35] https://www.odoo.com/groups?unsubscribe
>> [36] https://www.odoo.com/groups/community-59
>> [37] mailto:community@mail.odoo.com
>> [38] https://www.odoo.com/groups?unsubscribe
>> [39] http://factorlibre.com
>> [40] https://www.odoo.com/groups/community-59
>> [41] mailto:community@mail.odoo.com
>> [42] https://www.odoo.com/groups?unsubscribe
>> [43] https://www.odoo.com/groups/community-59
>> [44] mailto:community@mail.odoo.com
>> [45] https://www.odoo.com/groups?unsubscribe
>> [46] https://www.odoo.com/groups/community-59
>> [47] mailto:community@mail.odoo.com
>> [48] https://www.odoo.com/groups?unsubscribe
>> [49] https://www.odoo.com/groups/community-59
>> [50] mailto:community@mail.odoo.com
>> [51] https://www.odoo.com/groups?unsubscribe
>
> _______________________________________________
> Mailing-List: https://www.odoo.com/groups/community-59
> Post to: mailto:community@mail.odoo.com
> Unsubscribe: https://www.odoo.com/groups?unsubscribe
>