anchor.diff:  ====
   * {empty}
   +
  -.Update API comparison version in POM
  +.Update API reference version in POM
   [%collapsible]
   ====
   Update the parent-pom settings for API change reports setting `api_check_old_version` to the correct previous version to use.
  
positive.code: ====
  * {empty}
  +
  .Upload artifacts from `target/checkout/target` to a subdirectory of the release staging spot
  [%collapsible]
  ====
  We have a spot at https://dist.apache.org/repos/dist/dev/uima/ for all the artifacts to be released via the Apache mirror system. This is where you put the release candidates.
  
  Be sure to copy artifacts from the build-from tag spot, which should have a path like: `...[top level project]/target/checkout/target`. Note this is **NOT** from `[top level project]/target`. Doing this will guarantee that you're posting the artifacts built from the tag (which could be different from the `release:prepare` build in /target if someone snuck in a svn commit at the right moment.)
  
  
negative.code: ====
  * {empty}
  +
  .Upload the update site to a subdirectory of the release staging spot and *commit* (*Caution:* the update site contains a `.svn` folder that needs to be removed!)  **(deprecated)**
  [%collapsible]
  ====
  **Deprecated:** Use auto-staging instead.
  
  FIXME: Eclipse update site process needs updating...
  
  For a general background on how we build P2 sites, including Composite update sites, see link:https://uima.apache.org/eclipse-update-site.html[eclipse-update-site] page.
  