As Roberta suggests, I can create the release1.3 branch. I think we want to include a pending change for the winODBC version number (https://github.com/apache/incubator-trafodion/pull/126). So, I'll wait a day or so and see if that change can be merged.
Once the release branch is created, we'll also want to change the next release version on the master branch. That will make sure we can distinguish builds coming from release branch and master branch. For the next release number, I believe the plan includes moving to HBase 1.x support, so perhaps we should also change our major number as well. I propose that the next release number be 2.0.0 rather than 1.4.0. Of course that change will come in a pull-request, so feel free to give feedback there as well as here on that proposal. --Steve > -----Original Message----- > From: Roberta Marton [mailto:[email protected]] > Sent: Friday, October 23, 2015 4:57 PM > To: [email protected] > Subject: Apache Trafodion release 1.2.0 changed to release 1.3.0 > > The decision has been made to change Apache Trafodion release 1.2.0 to > release 1.3.0. Generally, even numbered releases means more stable code. > An odd numbered release was chosen because we want to first test the > waters > with this release. That is, this release is an exercise to make sure we > can release Trafodion by following Apache standards. > > > > At this time, we will be creating a new release branch for Trafodion 1.3.0 > that will be used to build the release artifacts. A e-mail will be sent > when the new branch is available with usage details. > > > > Regards, > > Roberta
