openerp-community team mailing list archive

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

This is a VERY important topic, please don't let it die...

Don't expect OpenERP S.A. will improve on this situation any time soon.
They are too busy with new releases and social features...
We must keep reporting bugs and merge proposals on official branches, but
that is not enough...

If we as a community join efforts to keep up to date branches, we ALL will
save a lot of time and frustrations...

I am not an expert on launchpad, but if Stefan, Raphaël, Panos or any other
"master of the branches" shows me the way, I will do my best to follow...


Regards,
-Mario


On Wed, Nov 14, 2012 at 9:55 AM, Niels Huylebroeck <nh@xxxxxxxxxx> wrote:

>
>
>
> 2012/11/14 Fabien Pinckaers <fp@xxxxxxxxxxx>
>
>>
>> > I'm founding a lot of bugs with fix released but not being merged in
>> > the main branch. This is leading us and I suppose the rest of
>> > companies to have our own branch with those merges applied.
>>
>>
>> They are several reasons for this:
>>
>> 1) It's a problem of timing.
>>
>> When I do merge proposals, I merge several of them in my own branch
>> rather than directly in trunk. This allows to check with runbot and
>> codereview before pushing to trunk. But I mark as fix released in
>> launchpad when I put in my branch. (otherwise it's compelx to remind
>> which bug has been closed afterwards).
>>
>> My branch is merged to trunk a few hours after, after having checked
>> that runbot is green. Usually it just a matter of 24 hours.
>>
>> 2) we have pending fixes not yet merged in v6.1 that we directly merge
>> in v7.0:
>>
>> -> We started a few weeks ago to forward port and code review
>> improvements made on v6.1 through OPW requests to v7.0. We did a lot of
>> them (about 100), but still about 20 are missing. Search OPW in these
>> branches:
>>
>> https://code.launchpad.net/~openerp/openobject-addons/trunk/+activereviews
>>
>>
> Neither of these two answers actually tells us what we would like to hear:
> that bugs will be fixed in 6.0/6.1 where they started and where our
> customers are running today.
> When we propose a merge with 6.0/6.1 branches (and have OPW maintenance
> for them) we expect the merges to actually appear in the
> lp:openobject-addons/6.x branches.
>
> Last actual code change on 6.0: 11 october 2012 before that it was 22
> august 2012
>
> For 6.1 it is slightly better with around 3 fixes in a little over a week.
>
> The problem is merge requests are coming in faster than you can (are
> willing to?) handle them. I understand your priority for v7.0 release (it's
> only 2.5 months overdue now ;-) but you are neglecting your currently
> paying customers/partners by not incorporating the fixes your support teams
> create.
>
> This leads to often re-discovering of bugs (waste of our time) and
> occasionally to duplicate bug reports (waste of your time). It happens way
> to often that support points out it has already been fixed and link a merge
> proposal but that is not the way most people maintain their production
> server. They want one solid used/viewed by many branch. This ensures
> quality and progress for everyone.
>
>
> --
> Niels Huylebroeck
> Lead Architect   --   Agaplan
> Tel. : +32 (0) 93 95 98 90
> Web : http://www.agaplan.eu
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openerp-community
> Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openerp-community
> More help   : https://help.launchpad.net/ListHelp
>
>