Post-vote release checklist for version 3.0.0

[ctubbsii]

• Label this issue with the project that corresponds to this release version
• Git tasks
  • Create a signed rel/<version> tag (and push it)
  • Merge <version>-rc<N>-next branch into a maintenance branch (if maintenance is expected),
    and then into the main branch (and push them)
  • Remove *-rc* branches
• Nexus tasks
  • Release the staging repository corresponding to the successful release candidate (use "release" button)
  • Drop any other staging repositories for Accumulo (do not "release" or "promote" them)
• SVN / dist-release tasks
  • Upload the release artifacts (tarballs, signatures, and .sha512 files) for the mirrors
  • Remove old artifacts from the mirrors (after updating the website)
• Board reporting tool
  • Add the date of release (the date the release artifacts were uploaded to SVN UTC+0000)
• Verify published artifacts
  • In Maven Central
  • In ASF Downloads
  • In several mirrors or CDN
• Update the website
  • Release notes
  • Add LTM: true to the release notes front-matter for LTM releases
  • Navigation
  • Downloads page
  • If LTM release, update previous LTM release entry on downloads page and release notes with an EOL date 1 year from the current release date
  • DOAP file
  • Add manual/examples/javadoc (build javadoc from tag with mvn clean package -DskipTests javadoc:aggregate -Paggregate-javadocs using at least JDK 17)
  • Add updated properties documentation (see the website README)
  • Jekyll config
  • Grep for, and update any links to previous version to now point to the new version
  • Update any older release notes front-matter to indicate they are either archived: true or archived_critical: true
• Announcement email
  • Prepare and get review on dev list (see examples from previous announcement messages)
  • Send to announce@apache.org and user@accumulo.apache.org (use plain text mode only; html email will be rejected)
• GitHub wrap-up
  • Close this issue
  • Create a new "Automated Kanban" project for the next version (if necessary) and move any open issues not completed in this release to that project
  • Close the project that corresponds to this release
• Twitter - TweetDeck is no longer available, so these can't be done.
  • Tweet it
  • Confirm the tweet

[ctubbsii]

I can't really complete the uploading of the javadoc and server properties, until the website is redesigned to accommodate the 3.x documentation, which starts to diverge from the 2.x docs. That redesign is somewhat substantial, and can't be done as a simple website update for the release, because there is a Jekyll plugin written in ruby that writes the links to the documentation, and changing that is non-trivial.

[ctubbsii]

Can't use TweetDeck anymore to post announcements on Twitter, so those actions can't be checked off. I'll probably remove them from this issue template.

[ctubbsii]

I did upload the javadoc and properties config, but I had to manually edit some of them to get them to make sense in the 2.x-centric docs. The site still needs a redesign to accommodate the docs better across major releases, but this is good enough for now.