anchor.diff:  ====
   * {empty}
   +
  -.Update the version in the `uimaj-eclipse-update-site`
  -[%collapsible]
  -====
  -FIXME: Eclipse update site process needs updating...
  +.Update the version in the `uimaj-eclipse-update-site` **(deprecated)**
  +[%collapsible]
  +====
  +**Deprecated:** Use Tycho instead to build update sites along with every regular build.
   
   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.
   ====
   * {empty}
   +
  -.Set `dropPrevVersions` to `true` in the `uimaj-eclipse-update-site` POM
  -[%collapsible]
  -====
  -FIXME: Eclipse update site process needs updating...
  +.Set `dropPrevVersions` to `true` in the `uimaj-eclipse-update-site` POM **(deprecated)**
  +[%collapsible]
  +====
  +**Deprecated:** Use Tycho instead to build update sites along with every regular build.
   
   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.
   ====
   * {empty}
   +
  -.Build the `uimaj-eclipse-update-site` module with {{-Papache-release}}
  -[%collapsible]
  -====
  -FIXME: needs update!
  +.Build the `uimaj-eclipse-update-site` module with {{-Papache-release}} **(deprecated)**
  +[%collapsible]
  +====
  +**Deprecated:** Use Tycho instead to build update sites along with every regular build.
   
   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.
   
  
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.
  