openerp-community-leaders team mailing list archive

[Savyn Vydelingum <Savyn@xxxxxxxxxxxxxxxxxxxxxx>]

Dear Everyone,

I have been following this email thread closely and very interesting arguments.  

I believe that the reasons, patches are not implemented is simply because Tiny has limited resource to do proper testing (and therefore it is ignored) and they are overwhelm with request (Sales, Support, community, training etc etc), and at the same time a blow that partners and the community are fixing issues that been pending and reported many times. 

In a democratic world, I would expect Tiny to respond to these issues and explain the path they wish to take and utilise the resource of the community and partners to fix these bugs and improve the application.  I think if Fabian as the leader of Tiny, could explain how he would like to receive help, to make the codes better, fix bug and improve the features, get an amazing web interface, then we could have a more productive approach.  Also the editor should allow a level of leniency and accept that it is time to allow us to help...otherwise everyone can fork and would not help anything.  

A possible simple approach would be:

-To have a list of bugs (I know it is in launchpad) but re-submit everything from x version.
-Vote for a person to be leader of this bug reporting db. Not Tiny (Senior Partners with a senior community/good contributor)
-The submitted bug is rated by leader. The mode win (lets say the top 10 reported bugs)
-The voted leader, push back the top 10 bug to the people to fix, documentation is DEFINITELY required from the prtner and community on how, what and why they wrote the bug fix this way.
-A fix bug is tested by the community expert leader
-Submit to Tiny
-Tiny to test and apply to branch.  
-Bug 11 and the rest move up the list, when top 10 are completed and not before.

Same process follows again

Tiny can then place deadline, create realistic road map and market when new patch over upgrade is being release (not upgrade with old bugs) etc.  

Fabian, the OpenERP partners and community are very helpful and I am sure we will all do our best to help and every email I see, this community is offering help.

My point here is for Tiny to agree on a process that our bug fix are implemented correctly and speedily.

I hope this make sense and have a great weekend everyone

kind regards
--
Savyn
________________________________________
From: openerp-community-leaders-bounces+savyn=publicus-solutions.com@xxxxxxxxxxxxxxxxxxx [openerp-community-leaders-bounces+savyn=publicus-solutions.com@xxxxxxxxxxxxxxxxxxx] On Behalf Of Ferdinand Gassauer [office@xxxxxxxxxx]
Sent: 22 January 2010 17:27
To: openerp-community-leaders@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Openerp-community-leaders] Simple things we need from Tiny for    better bug planning/management

In respect of getting patches in - it's probably a question of "karma" - (not necessary the one in Launchpad.)

Very often my "little", often trivial patches get now integrated very soon (some days) thanks to Jay.

So TIny makes a big effort compared to some time ago.

for some more complex patches like commit on sequences or rounding discussed else where we need to set up a peer review and - may be using the test suite OpenERP Scenario<https://launchpad.net/oerpsenario/> (thanks to c2c) which must pass running against db using real data (of partners and/or typical clients)

And the results should be documented on a per reviewer basis (quality control).

* passed

* failed

* not relevant (Example we only use EUR but Camp2camp tests multicurrency invoices)

--

Best Regards

ChriCar Beteiligungs- und Beratungs- GmbH

http://www.chricar.at/ChriCar/index.html

Dr. Ferdinand Gassauer

Official Tiny Partner