openerp-community team mailing list archive

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

Thanks for your help.

I got farther this time.  I could assign the bug to OCB 6.1 and 7.0.
I could not link the branch with the fix to them (I guess because 
original fix is applied to trunk, not 6.1 or 7.0)

Should I  branch out 6.1 and 7.0, apply the fix and propose for merge, 
or the original fix can be applied to them ?

Regards,
-Mario

On 04/11/2013 03:45 PM, Stefan Rijnhart wrote:
> On 04/11/2013 08:20 PM, Mario Arias wrote:
> > I just tried to follow your step by step, and assign them to OCB, but 
> > could not figure out how to handle different series...
>
> Hi Mario,
>
> where do you get stuck? Do you get to the point where you click 
> 'Target to series'? You should be able to choose between 6.1 and 7.0 
> in the next screen. Note that you can only do so when you view the bug 
> in the backports project. That is the difference between
>
>     https://bugs.launchpad.net/ocb-addons/+bug/949078
>
> and
>
>     https://bugs.launchpad.net/openobject-addons/+bug/949078
>
> After you selected the backports project using the 'Also affects 
> project' link, the url changes accordingly so you should be able to 
> choose a series at that moment.
>
> By the way I did not get any notifications of bugs assigned to the 
> backports projects in the last couple of hours so it may be the case 
> that you ended up with the wrong project.
>
> > Besides, as for 6.1 series...  We continue to have the official 
> > branches, so the policy stays the same: post bugs/MPs on official 
> > series AND then relate them to OCB ones, right ?
>
> Well, that is an interesting point. For releases still supported by SA 
> that is a definite yes, but 6.1 is practically unsupported by now. 
> Apart from the occasional OPW, no changes are committed anymore 
> against its branches. Even the nightly synchronization of translations 
> has already stopped for two of the three projects.
>
> Now it is either the case that the bug still exists in 7.0/trunk, or 
> else it has been fixed in the meantime. In the former case you should 
> probably test if the fix works against the newer release and propose 
> against *that* official branch. In the latter case, the fix you 
> propose to backports should ideally reflect the changes that 
> constitute the fix in the newer release, at least if they are atomic 
> (i.e. not a big refactoring).
>
> So this is only an issue if the fix for 6.1 does not apply to 7.0 or 
> if the piece of code that contains the problem has been refactored 
> out. I am not sure what the use would be of an MP against an official 
> but by now unsupported branch in that case, to be honest.
>
> Cheers,
> Stefan.