openerp-community team mailing list archive

[Mario Arias <the.clone.master@xxxxxxxxx>]

Hi Olivier,

Just one personal sample, there are plenty if you take a look under 
"wish-list"...
https://bugs.launchpad.net/openobject-addons/+bug/1132963

I reported a problem with payroll, that makes real use impossible 
because it fails to provide correct contracts for employees.  It is just 
a "no brain" fix: add an "&"  (and) to an expression...

It just made it to trunk, and even there is still pending for merge 
(more than seven months ago) so it is still impossible to really use 
full payroll features (a shame such a great module is broken by so 
simple issues...).  Why not fix in 7.0/6.1?  Easy... no related OPW...
And before someone comments about not having OPW...  I am not asking to 
get services for free...  I reported a bug AND the fix, that I already 
have applied on my installations, driving payrolls with more than 300 
employees...  I am contributing....


What about OCB branches...  fixed!


I don't want to argue with S.A., all I ask is that OCB branches (or 
series if moved somewhere else)  stay open to contributions, something 
that official ones are not...


Regards,
-Mario



On 10/25/2013 10:57 AM, Olivier Dony wrote:
> On 2013-10-25 17:43, Mario Arias wrote:
> > Reason to be for OCB branches is that official ones are not 
> > "community friendly"...
> >
> >   * Lots of bugs with even corresponding MPs that are rejected and/or 
> > ignored...
> >   * Changes needed to really fix a bug that are not accepted because 
> > of the "no
> >     change to model", but not fixing is worse...
>
> I strongly disagree with those statements. The OpenERP stable policy 
> is here to protect customers, but OpenERP SA also offers a bugfix 
> guarantee to the customers. So no, the policy can never be an excuse 
> for not fixing a real bug.
>
> I should know because it's my job. I've been dealing with dozens of 
> bug reports and maintenance tickets every single week for the past few 
> years (qualifying reports, reviewing patches, helping to write 
> patches, etc.), and enforcing the policy at the same time. And I've 
> never encountered a *real* bug that we refused to fix, policy or not. 
> If you have, please send me the bug number or maintenance ticket 
> number so I can verify it!
>
> Actually, in most case it only takes a few more minutes of thinking 
> for an OpenERP engineer to find a valid fix that does not violate the 
> stable policy.
> And if we ever come across a bug that *really* requires a model 
> change, we can always find alternatives like shipping them as extra 
> auto-install modules.
>
> On the other hand I *have* encountered countless cases of regressions 
> and errors caused by casual changes committed on a stable branch, 
> which is the very reason why the policy is in place.
>
> No, the policy is not designed to make our lives simpler, and it often 
> makes fixing bugs a bit more difficult! But it's definitely worthwhile 
> in order to offer true stability to the customers. Have you tried 
> OpenERP 5.0 at the time where every bugfix was commited directly into 
> the stable branch without any review nor policy?!
>
> And finally no, the great majority of OpenERP deployments are not 
> under the active supervision of OpenERP Partners or competent OpenERP 
> technicians, despite what some people want to believe. Just do the maths!