hi
I would like to continue the discussion from this forum thread here:
1749443
Brian Duff:
For backports, you should not have to re-request for every version. Be sure to request a backport, and not a one-off fix. One-off fixes are exactly what they imply - they don't get committed into the branch.
Jan Vervecken:
That is a distinction that has never been mentioned in the my service requests in the past.
So, are you saying that backports end up in any next release automatically?
Brian Duff:
If I understand the process properly, then yes. Backports are supposed to be merged from our MAIN branch (for 11) into the 10.1.3.x development branch, and should therefore show up in all future releases on the 10.1.3 stream.
There was a glitch in the way we branched 10.1.3.1.0 that might have messed with this process somewhat - though I'm not sure if that's the reason you had to re-request fixes for 10.1.3.2.0 (if you let me know SR and bug numbers, I'd be glad to investigate further if you like). At any rate, the branching glitch was reset for 10.1.3.3.
---
Thanks for your reply Brian.
I will try to find the numbers, so you can take a look a this.
regards
Jan Vervecken