Thanks Ted! Yeah we need to wind down the rate of changes for 1.3.1 and actually wrap it up. First need to make sure CI builds are stable, because for the past month they really have not been so. Then I was going to go over the git history and compare it with what's marked as "fixedV=1.3.1" in Jira to see.
-Mikhail On Thu, Feb 16, 2017 at 11:19 AM, Enis Söztutar <[email protected]> wrote: > We also need to ensure that no jira has creeped into the release which > should not be there. I used to do create release notes again, and do a diff > against the version from the actual release tarball to make sure that if > any jira is marked with the fix version after the release. > > Enis > > On Thu, Feb 16, 2017 at 8:39 AM, Ted Yu <[email protected]> wrote: > > > I have made the change. > > > > FYI > > > > On Thu, Feb 16, 2017 at 8:26 AM, Sean Busbey <[email protected]> wrote: > > > > > yes, it should be. with a release date of 01/17/2017. > > > > > > Anyone with admin rights on the jira project should be able to do this. > > > > > > Thanks Ted! > > > > > > On Thu, Feb 16, 2017 at 10:46 AM, Ted Yu <[email protected]> wrote: > > > > Hi, > > > > Currently version 1.3.0 shows up in the JIRA as Unreleased Version. > > > > > > > > Should it be marked as Released ? > > > > > > > > Cheers > > > > > > -- Thanks, Michael Antonov
