trafodion-development team mailing list archive
-
trafodion-development team
-
Mailing list archive
-
Message #00011
Fixes to be put on release branch?
-
To:
"Zeller, Hans" <hans.zeller@xxxxxx>, "Goyal, Narendra (SeaQuest R&D)" <Narendra.Goyal@xxxxxx>, "Anderson, Marvin" <marvin.anderson@xxxxxx>
-
From:
"Birdsall, Dave" <dave.birdsall@xxxxxx>
-
Date:
Mon, 14 Jul 2014 17:56:36 +0000
-
Accept-language:
en-US
-
Cc:
"Jain, Rohit \(Trafodion\)" <rohit.jain@xxxxxx>, "Messavussu, John" <john.messavussu@xxxxxx>, "Mishra, Atanu" <atanu.mishra@xxxxxx>, "Trafodion-Technical-Committee@xxxxxxxxxxxxxxxxxxx" <Trafodion-Technical-Committee@xxxxxxxxxxxxxxxxxxx>, "Le Rouzo, Christophe" <christophe.le-rouzo@xxxxxx>, "Trafodion-Development@xxxxxxxxxxxxxxxxxxx" <Trafodion-Development@xxxxxxxxxxxxxxxxxxx>
-
Thread-index:
Ac+fi7XiSO8KyvVXT8y8rFHp0Fsxsw==
-
Thread-topic:
Fixes to be put on release branch?
Hi Release Managers,
One thing we need to be proactive about is encouraging developers to submit fixes to the new release branch if they aren't already there and we think they are critical.
Two that come to my mind are:
1. Jim Capp's change to disable native expressions (core)
2. Marvin Anderson's change to fix install for single node systems (install).
Do you agree? And, Marvin, for your change, would we need Amanda Dierickx install change as well?
Thanks,
Dave
Follow ups
