Community mailing list archives

community@mail.odoo.com

Re: The issue mountain on github

by
OpenERP Master
- 07/29/2015 15:45:42
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> 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/
> *mERP |** Odoo Android App | *_merpapp.com _
>
> /// site  : xpansa.com 
> /// mail  : eva.pinter@xpansa.com <mailto:roman.gurinovich@xpansa.com>
> /// phone, IE : +44 (0)7596 40 30 99
> /// skype : epinter
>
>> On 29 Jul 2015, at 01:02, Antony Lesuisse <al@openerp.com
>> <mailto:al@openerp.com>> 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 >> >> 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 : >> >> 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/ [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 <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 <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 >> > >> >> _______________________________________________ >> Mailing-List: https://www.odoo.com/groups/community-59 >> Post to: mailto:community@mail.odoo.com >> Unsubscribe: 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 >

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe