| Re: [tcf-dev] Any fixes to backport for tcf-1.2.1 ? |
|
Hi Martin,
In the “Agent side” list, only is OK to backport – if somebody really needs it. Others are not suitable for backporting – they don’t really fix anything in 1.2, and can cause a regression.
In general, I suggest to backport fixes into maintenance branch only when it is explicitly requested by users, e.g. through Bugzilla.
Regards, Eugene
From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Oberhuber, Martin
Hi all,
Luna SR1 is soon wrapping up (RC3 build this Monday).
We haven’t contributed anything so far, but I was wondering if we should backport any important fixes ?
Uwe had already set up a Hudson job for 1.2.x so the backports should get built + unit-tested automatically so the risk should be small. If there’s anything committed to the 1.2_luna branches by Tuesday morning my time I would contribute a build to Luna SR1 – if not we’d just keep our 1.2.0 release out there.
We should focus on hi-priority and regression fixes. Here are some candidate fixes from my point of view Host side:
Agent side:
Feel free to nominate other fixes.
We need to move fast if a Luna SR1 contribution is desired.
Thanks, Martin -- Martin Oberhuber, SMTS / Product Owner – Development Tools, Wind River direct +43.662.457915.85 fax +43.662.457915.6
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately. |