openerp-community-committers team mailing list archive

[Carlos Liebana <carlos.liebana@xxxxxxx>]

<my comments>

A1: I don't see OpenERP taking responsability for these bugs.
A2: First of all and as we're all commiters/developers, we have to make a
list of non-closed annoying bugs on v5 and compromise to solve them.
A3: Anyway, Bugs by duplicate in this branch and in the official ones is a
problem... Can't be them "reassigned" to this one?

Anyway, right now what we all have clear is that we have to focus on
developping a new v5 release taking care of those bugs already non-solved by
OpenERP SA., and after that focus on bugs that would come.

So, I think right now we should follow these points:
- Make a wishlist (in a google doc, for example) with all the non-solved
bugs already known.
- Assign the development to one of us and the checkings of the fixes to
another of us.
- Once all the bugs in wishlist are solved, compile and launch our 5.0.15.1,
or/and propose the merging of the whole branch to the official one (would
OpenERP SA accept this?)

After that, we can do a monitorization until there are again new open bugs,
and repeat the process again.

</my comments>

2010/11/18 Jan Verlaan - Veritos <jverlaan@xxxxxxxxxx>

> Dear members,
>
> during my first bugsolving regarding the this new community branche I did
> run in some unclearnesses.
> As we are branch member of project openobject-addons all bugs are created
> in this project. So far so good.
>
> Q1 - Who is first responsible for reviewing the bugreports?
> A1 - In my opinion OpenERP should still take the lead. We watch and
> eventually make a merge proposal for community branch if needed.
>
> Q2 - How do we track specific bugs regarding or own branch? Our branch will
> slowly differ from OpenERP's one. We can expect bugs specific to our own
> branche. Does OpenERP close those bugs or will they reassign to us? Where
> should the reassign go to? (see Q3 also)
> A2 - ?
>
> Q3 - How do we track important bugs not taken care by OpenERP SA because no
> MC-user reports it, but community wants to solve it? Those bugs can get a
> status by OpenERP SA resulting that bug is falling into background.
> A3 - There should be a possibility to assign this bug to or own project
> (not available yet).
> For example bug 671172, status is set to wishlist in addons with milestone
> to V6 by OpenERP, but I have created a merge proposal now for community
> branch, but can not handle the bug status. We do need a own project so we
> can link via "Also affect project" to or own project and set that status
> differently as for V6
>
> What are your thoughts?
>
> With kind regards,
> Jan Verlaan
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-community-committers<https://launchpad.net/%7Eopenerp-community-committers>
> Post to     : openerp-community-committers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-community-committers<https://launchpad.net/%7Eopenerp-community-committers>
> More help   : https://help.launchpad.net/ListHelp
>



-- 
*CARLOS LIÉBANA ANERO*
*ting! - Director*
Tlfno.: 987086950
Mov.: 673335808
Twitter: @carlosliebana
www.ting.es