The problem with the JIRA release notes is that there are a lot of issues marked as 0.6.2 that are now 0.7.0 issues. I can add the 0.6.2 label to unlabeled issues, but I don't seem to have permission to create a 0.7.0 version to move incorrectly-labeled issues. Can you or anyone with permission create a 0.7.0 version?
On 11/12/13 10:00 AM, "kishore g" <[email protected]> wrote: >Do we have the release notes, we can generate it from the JIRA. It ensures >that all tickets marked for 0.6.2 are closed. > >I will review this today. > >Thanks a lot for taking this up. > > >On Mon, Nov 11, 2013 at 11:50 PM, Kanak Biscuitwala ><[email protected]>wrote: > >> Hi, >> >> We're planning to conduct two near-simultaneous releases, 0.6.2 and >>0.7.0. >> This email is for voting on the 0.6.2 release, which mostly consists of >> security and stability fixes, as well as minor feature improvements. >>Here >> is a list of issues that 0.6.2 addresses: >> >> 1. rebalance/ideal state fixes: >> HELIX-150/141/147/148/151/153/154/166/173/205/216/273/277/280 >> 2. zk-session expiry handling fix: HELIX-169/170/171/195/124/28/123/279 >> 3. security fixes: HELIX-257/258 >> 4. zkclient&close() fix: HELIX-264 >> 5. state model leak fix: HELIX-197 >> 6. state model validation: HELIX-144 >> 7. integration test support: HELIX-285 >> 8. YAML cluster setup: HELIX-215 >> 9. project quality improvements: HELIX-70/198/207/218 >> >> The release is currently staged at >> https://dist.apache.org/repos/dist/dev/incubator/helix/ and is signed by >> my key (see the KEYS file). >> >> Vote: >> >> * +1 to approve the 0.6.2-incubating release >> * 0 to indicate indifference towards the 0.6.2-incubating release >> * -1 to reject the 0.6.2-incubating release >> >> This poll will remain open for at least 72 hours from now. A final score >> of 3 or greater is required to proceed with the release. >> >> Thanks, >> Kanak
