Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Task marked incomplete

...

  •  Get feedback from the community on the scope of the release
    email has been sent to dev@hawq.incubator.apache.org on Dec 20th, 2016, no objections so far.
  •  Versions created on Apache HAWQ JIRA
    2.2.0.0-incubating & 2.3.0.0 version have been created in JIRA
  •  Request bulk update permissions from Apache Infrastructure team. It turns out the default workflow in play "Classic default workflow + FixVersion required" does not allow editing of JIRAs in a Closed state.
  •  Move all JIRAs referencing a version (affected/fix) of 2.1.0.0-incubating to 2.2.0.0-incubating.
  •  Publish Apache HAWQ 2.2.0.0-incubating Release Dashboard and announce it's availability on dev list (dev@hawq.incubator.apache.org).
  •  Details of this release posted on wiki (this page).
  •  Create JIRA to update version strings: 
    Jira
    showSummaryfalse
    serverASF JIRA
    serverId5aa69414-a9e9-3523-82ec-879b028fb15b
    keyHAWQ-1232
     
  •   After version string update (
    Jira
    showSummaryfalse
    serverASF JIRA
    serverId5aa69414-a9e9-3523-82ec-879b028fb15b
    keyHAWQ-1232
    ) has been committed, create release branch "2.1.0.0-incubating"

  •  Update "getversion" file with "-incubating" version suffix (2.1.0.0-incubating) in the release branch: 
    Jira
    showSummaryfalse
    serverASF JIRA
    serverId5aa69414-a9e9-3523-82ec-879b028fb15b
    keyHAWQ-1236

  •  Move all Open JIRAs with Fix Version of "2.2.0.0-incubating" to "2.3.0.0-incubating".
  •  Start release artifact creation process
  •  Send RC1 for dev PMC vote
  •  Get results of RC1
  •  Fix RC1 issues
  •  Send RC2 for dev PMC vote