Should I have it linked to 6.1 on official branch first, or can I link
it to OCB and then choose both 6.1 and 7.0 series ?
do the latter, because as Stefan pointed out, it looks like nothing much is
ever going to happen with the official 6.1 branches
--
Therp - Maatwerk in open ontwikkeling
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
On 04/12/2013 08:40 AM, Mario Arias wrote:
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
On 04/12/2013 10:13 AM, Carlos LiƩbana wrote:
Anyway, everybody is welcome to add the tag ocb-stock-v1 in those
existing bugs you're aware of regarding stock management. Everybody is
also welcome to get them fixed, we are starting in our side with some
of them.
Great, looking forward to
Hi,
as discussed on this list, the 6.1 series have been opened on the
backports projects. The branches from our old project have now been
pushed and linked to the series. Two new FAQs have been created
mentioning the origin of the 6.1 branches and the functional changes in
them so that you
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
Hi Stefan,
Sorry for asking so basic questions about LP, but I was so frustrated
about reporting errors for official branches, that I didn't take the
time to learn the whole process, and started fixing the errors directly
on our own repositories as patches (faster and a less frustrating)
I
7 matches
Mail list logo