+1 Best Regards, Kevin Xu
-----Original Message----- From: Hans Zeller [mailto:[email protected]] Sent: Friday, January 26, 2018 4:34 AM To: [email protected] Subject: RE: [VOTE] Apache Trafodion release 2.2.0 RC 2 +1 (non-binding) Based on testing the previous RC on an Amazon VM. -----Original Message----- From: Liu, Ming (Ming) [mailto:[email protected]] Sent: Thursday, January 25, 2018 7:22 AM To: [email protected] Subject: [VOTE] Apache Trafodion release 2.2.0 RC 2 Hi to everyone in the Trafodion Community, This is a call to vote on release 2.2.0 of Apache Trafodion . This is a major release and includes over 300 fixes and some important features. The highlights are all documented here: https://cwiki.apache.org/confluence/display/TRAFODION/Release+2.2 They include : * Trafodion graduates as top level Apache project * DTM enhancements by porting EsgynDB DTM changes to Trafodion * jdbcT4 for publish to maven central * Trafodion Elasticity enhancements * LOB support in JDBC * RMS enhancements * Bug fixes JIRA Release Notes : Trafodion 2.2 JIRA Release Notes https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318620&version=12338559 Highlights : https://cwiki.apache.org/confluence/display/TRAFODION/Release+2.2 GIT info: The tag for this candidate is "2.2.0rc2". Git repository: git:// git.apache.org/trafodion.git Release artifacts : https://dist.apache.org/repos/dist/dev/trafodion/trafodion-2.2.0-RC2/ Artifacts are signed with my key : E1502B16 which is in https://dist.apache.org/repos/dist/release/trafodion/KEYS Instructions : Installing Trafodion using convenience binaries using the Python installer or install with Ambari : http://trafodion.apache.org/docs/provisioning_guide/index.html Setting up build environment and building from source : https://cwiki.apache.org/confluence/display/TRAFODION/Create+Build+Environment https://cwiki.apache.org/confluence/display/TRAFODION/Build+Source [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Vote will be open until the community has had a chance to try out the instructions and we get sufficient feedback ( at least 72 hours), unless cancelled. Thanks, Ming
