openerp-community-leaders team mailing list archive
-
openerp-community-leaders team
-
Mailing list archive
-
Message #00054
Re: Simple things we need from Tiny for better bug planning/management
Jan Verlaan - Veritos wrote:
I totally agree with your exposition, Niels :-). But wouldn't it be
nice IF community AND Tiny could work in same branch?
That would be a win-win situation. Both parties don't have to backport
to each version.
>From that point of view I asked my previous question: " Has someone
asked Tiny already to let the community commit their fixes into the so
called "stable" which is actually un-stable?"
If we have no answer to this question, it would be the first step to
get one, before any other step we want to take.
Regards,
Jan
Working together with Tiny is the ultimate goal ofcourse, but at the
moment I think frustration from people who supply bugfixes only to see
them not getting integrated would want to see more than just a promise
of better integration.
Fabien himself should get these emails as he too is member of
openerp-community-leaders and it would be hard to imagine he would not
notice this stream of mails all on this topic.
Also the original idea for openerp-community-leaders was that they would
represent the more involved members of the community which should be
able to take decisions etc regarding bugs and long term design, but to
this day noone except the OpenERP Quality Team (
https://launchpad.net/~openerp ) has commit rights to the stable and trunk.
Regards,
Niels
References