Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id C15D5200BCA for ; Mon, 21 Nov 2016 17:24:38 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id BFFD9160AF9; Mon, 21 Nov 2016 16:24:38 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id AB115160B1F for ; Mon, 21 Nov 2016 17:24:36 +0100 (CET) Received: (qmail 26874 invoked by uid 500); 21 Nov 2016 16:24:35 -0000 Mailing-List: contact commits-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@accumulo.apache.org Delivered-To: mailing list commits@accumulo.apache.org Received: (qmail 26588 invoked by uid 99); 21 Nov 2016 16:24:35 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Nov 2016 16:24:35 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 3C552F0DC1; Mon, 21 Nov 2016 16:24:35 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: mwalch@apache.org To: commits@accumulo.apache.org Date: Mon, 21 Nov 2016 16:24:39 -0000 Message-Id: In-Reply-To: <9c89bafc5693475c9e48218bcb9e4845@git.apache.org> References: <9c89bafc5693475c9e48218bcb9e4845@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: [05/16] accumulo git commit: Jekyll build from gh-pages:a71ede8 archived-at: Mon, 21 Nov 2016 16:24:38 -0000 http://git-wip-us.apache.org/repos/asf/accumulo/blob/59a6d65d/release/accumulo-1.6.1/index.html ---------------------------------------------------------------------- diff --git a/release/accumulo-1.6.1/index.html b/release/accumulo-1.6.1/index.html index 7935522..ab71493 100644 --- a/release/accumulo-1.6.1/index.html +++ b/release/accumulo-1.6.1/index.html @@ -93,13 +93,13 @@
  • Documentation
  • @@ -108,30 +108,11 @@
  • Get Involved
  • Mailing Lists
  • People
    • -
  • News Archive
    • -
  • Community Projects
    • -
  • Thanks
    • +
  • Related Projects
    • +
  • Contributor Guide
  • Governance
    • -
  • - Development - -
    • @@ -166,9 +147,19 @@

      Apache Accumulo 1.6.1 is a maintenance release on the 1.6 version branch. This release contains changes from over 175 issues, comprised of bug-fixes, performance -improvements and better test cases. As this is a maintenance release, Apache Accumulo -1.6.1 has no client API incompatibilities over Apache Accumulo 1.6.0. Users of 1.6.0 -are strongly encouraged to update as soon as possible to benefit from the improvements.

      +improvements and better test cases.

      + +

      Below are resources for this release:

      + + + +

      As this is a maintenance release, Apache Accumulo 1.6.1 has no client API incompatibilities +over Apache Accumulo 1.6.0. Users of 1.6.0 are strongly encouraged to update as soon as +possible to benefit from the improvements.

      New users are encouraged to use this release over 1.6.0 or any other older releases. For information about improvements since Accumulo 1.5, see the 1.6.0 release notes.

      http://git-wip-us.apache.org/repos/asf/accumulo/blob/59a6d65d/release/accumulo-1.6.2/index.html ---------------------------------------------------------------------- diff --git a/release/accumulo-1.6.2/index.html b/release/accumulo-1.6.2/index.html index 81d002d..22f65d7 100644 --- a/release/accumulo-1.6.2/index.html +++ b/release/accumulo-1.6.2/index.html @@ -93,13 +93,13 @@
    • Documentation
    • @@ -108,30 +108,11 @@
    • Get Involved
    • Mailing Lists
    • People
      • -
    • News Archive
      • -
    • Community Projects
      • -
    • Thanks
      • +
    • Related Projects
      • +
    • Contributor Guide
    • Governance
    -
  • - Development - -
    • -
  • - Development - -
    • -
  • - Development - -
    • -
  • - Development - -
    • -
  • - Development - -
    • -
  • - Development - -
    • -
  • - Development - -
    • -
  • - Development - -
    • -
  • - Development - -
    • -
  • - Development - -
    • http://git-wip-us.apache.org/repos/asf/accumulo/blob/59a6d65d/releasing.html ---------------------------------------------------------------------- diff --git a/releasing.html b/releasing.html index 3c3da5f..a85e0f5 100644 --- a/releasing.html +++ b/releasing.html @@ -1,322 +1,10 @@ - - - + - - - - - - - -Making a Release - - - - - - - - - - - - -
      -
      -
      - - -
      - -

      Making a Release

      - -

      This is a guide for the creation of a release of Apache Accumulo.

      - -

      Setup

      - -

      There are number of things that are required before attempting to build a release.

      - -
        -
      1. Use gpg-agent, and be sure to increase the gpg-agent cache timeout (via .gnupg/gpg-agent.conf) to ensure that the agent doesn’t require re-authentication mid-build, as it will cause things to fail. For example, you can add default-cache-ttl 6000 to increase the timeout from the default of 10 minutes to over an hour. If you do not have a GPG key, reference the very thorough ASF release signing documentation.
        2. -
      2. Ensure that you’re using the correct major release of Java (check javadoc too).
        3. -
      3. Ensure that you’re building Apache Accumulo with a username that has the same name as your Apache ID (this is due to -the maven-release-plugin and staging the release candidate).
        4. -
      4. Update the CHANGES file so that it’s in sync with Jira (manual process).
        5. -
      5. Ensure that you have a texlive distribution installed so you are able to build the documentation.
        6. -
      6. Have a clean workspace before starting.
        7. -
      - -

      Given all of this, it’s recommended that you only attempt making a release from a GNU/Linux machine.

      - -

      Create the candidate

      - -

      TL;DR

      - -
        -
      • ./assemble/build.sh --create-release-candidate to make the release candidate
        • -
      • git tag $version $version-rcN to create an RC tag from the actual tag
        • -
      • git tag -d $version make sure you don’t accidentally push a “release” tag
        • -
      • git push origin $version-rcN push the RC tag
        • -
      • git checkout -b $version-rcN-branch save off the branch from the Maven release plugin
        • -
      • VOTE
        • -
      • If vote fails, fix the original branch and start over.
        • -
      • If vote passes, git merge $version-rcN-branch back into the original branch you released from.
        • -
      • git tag -s $version-rcN $version make a GPG-signed tag
        • -
      • git push origin $version push the signed tag.
        • -
      - -

      Long-winded explanation

      - -

      You should use the provided script assemble/build.sh to create the release candidate. This script is -desirable as it activates all necessary maven profiles in addition to verifying that certain preconditions -are met, like RPM signing availablilty and the ability to sign files using GPG. The –test option can -be used as a dry run for creating a release candidate. The –create-release-candidate option should be -used to create the actual release candidate.

      - -

      When invoking build.sh with the –create-release-candidate option, the majority of the work will be performed -by the maven-release-plugin, invoking release:clean, release:prepare, and release:perform. These will -guide you through choosing the correct versions. The default options provided should be what you choose. -It is highly recommended that an ‘RC’ suffix is not appended to the release version the plugin prompts -you for, as that will result in that version string being placed into the poms, which then would require -voting to occur on artifacts that cannot be directly promoted. After the build.sh script finishes (this will -likely take at least 15 minutes, even on recent hardware), your current branch will be on the “next” version -that you provided to the release plugin.

      - -

      One unwanted side-effect of this approach is that after creating this branch, but before invoking release:perform, -you must edit the release.properties to add the -rcN suffix to the value of scm.tag. Otherwise, the release -plugin will complain that it cannot find the branch for the release. With a successful invocation of mvn release:perform, -a staging repository will be made for you on the ASF Nexus server which you can log into with your ASF -credentials.

      - -

      After you log into Nexus, click on Staging Repositories in the Build Promotion toolbar on the left side of -the screen. Assuming your build went according to plan, you should have a new staging repository made for -you. At this point, you should inspect the artifacts that were staged to ensure that they are as you expect -them to be. When you’re ready to present those artifacts for voting, you need to close that repository which -will make it publicly available for other members to inspect.

      - -

      Vote

      - -

      At this point, you should have a closed repository that’s ready to vote on. Send a message to the dev -list and get the ball rolling. If the vote ultimately fails, you delete -the staged repository, clean up the branch you created (or wait until the release ultimately passes if you -choose), and fix what needs fixing.

      - -

      If the vote passes, huzzah, you’re almost done.

      - -

      Promote the artifacts

      - -

      Promote that staged repository using Nexus which you can do with the click of a button. This will trigger -a process to get the release out to all of the mirrors.

      - -

      Create the final Git tag

      - -

      The Git repository should also contain a tag which refers to the final commit which made up a release. This tag -should also be signed with your GPG key. To ensure proper retention on release (stemming from ASF policy -requirements), This final tag must being with “rel/”. For example, a release of 1.7.0 should have a corresponding -tag name of “rel/1.7.0”.

      - -

      Copy artifacts to dist.apache.org

      - -

      An SVN server is running at https://dist.apache.org/repos/dist/release/accumulo. You need to upload the release -tarballs, the GPG signatures and checksum files to the correct directory (based on the release number). If you -are releasing a bug-fix release, be sure to delete the previous release in the same line (e.g. if you release -1.6.2, remove 1.6.1). The old tarballs removed from dist.apache.org will still be preserved in archive.apache.org -automatically.

      - -

      Update projects.apache.org

      - -

      Fill out the add release form to update the projects website.

      - -

      Update the Website

      - -

      After a successful vote, this website needs to be updated with the new artifacts.

      - -
        -
      • Copy Accumulo User Manual (HTML version exists in >=1.7.0)
        • -
      • Update downloads page
        • -
      • Create release notes (ensure notes contain link to JIRA changes for that version)
        • -
      • Remove previous bug-fix release (if applicable)
        • -
      • Update examples README files
        • -
      • Update doap_Accumulo.rdf
        • -
      - -

      Javadocs

      - -

      Javadocs are easy to update. Using the latest JDK7 or later (at least JDK 7u21 -to avoid known vulnerabilities), follow these steps:

      - -
        -
      1. Unpack the source release tarball and change to its root directory, or checkout the SCM tag for the release
        2. -
      2. Build the javadocs with mvn clean package javadoc:aggregate -DskipTests -Paggregate-javadocs
        3. -
      3. Take note that the javadocs you will need to copy are the entire contents of ./target/site/apidocs/
        4. -
      4. Checkout the gh-pages branch (you may need to move the contents of ./target/site/apidocs outside your git workspace to switch branches)
        5. -
      5. Remove any existing apidocs from the appropriate version folder (e.g. 1.6/apidocs for a 1.6.x release)
        6. -
      6. Copy the entire contents of the new apidocs directory (identified in step 3) to the destination (e.g. to 1.6/apidocs)
        7. -
      7. Continue updating the site content, as needed
        8. -
      8. Commit the changes
        9. -
      9. Update the site using jekyll with ./_devtools/git-hooks/post-commit (if you don’t have the commit hook already configured)
        10. -
      10. Don’t forget to push both the gh-pages and asf-site branches
        11. -
      11. Verify that javadocs have been updated on the production site (e.g. https://accumulo.apache.org/1.6/apidocs/)
        12. -
      - -

      References

      - -

      Some good references that explain a few things:

      - - - - -
      - - - - - -
      -
      -
      - +Redirecting… + + +

      Redirecting…

      +Click here if you are not redirected. + http://git-wip-us.apache.org/repos/asf/accumulo/blob/59a6d65d/screenshots.html ---------------------------------------------------------------------- diff --git a/screenshots.html b/screenshots.html deleted file mode 100644 index 3b6c8b7..0000000 --- a/screenshots.html +++ /dev/null @@ -1,227 +0,0 @@ - - - - - - - - - - - - -Screenshots - - - - - - - - - - - - -
      -
      -
      - - -
      - -

      Screenshots

      - -
      -
      -The following is a screenshot of the Apache Accumulo™ monitor overview web page. Accumulo was running on an eleven node cluster. The continuous ingest test suite was running to generate load. Ten continuous ingest clients were running. -
      -
      - -monitor overview - -
      -
      - -
      -
      -The following screenshot shows the monitor master page. This page gives information about individual tables within accumulo. Continuous ingest is running against the table ci. -
      -
      - -monitor master - -
      -
      - -

      The data generated by the continuous ingest test suite looks like the following. The data is random, but forms many giant linked list. Each ingest client continually generates linked list containing 25 million nodes. In the shell session below a few scans are issued to start following the linked list that the first node in the table is part of.

      - -
      root@test15 ci> scan 
-000000000135fbbe 074c:569c []    2db1de18-cd37-407d-b060-481a0a214c90:000000002b2bcfe1:2e15cb9f62fd22ab:fe6f84c7
-000000000d76dcc9 4f62:0647 []    65f401e8-4f93-498c-bffa-ecc21a8645fd:000000000e7c2bbc:6fad98d023b8f146:a2c4d59f
-0000000024e07be4 5e56:221d []    5283b4bd-4f18-4af9-a242-c8053b095e04:000000001e1ad441:12de1d82f4a7bf2f:ae231a6a
-000000003e13cb50 1d0a:415c []    5944afab-8407-4391-9994-91b313e545dd:0000000002d61c91:4890a8885e54b714:d542fafa
-00000000634d0aaa 310d:1e58 []    2db1de18-cd37-407d-b060-481a0a214c90:000000000c9e8018:4111345bc9afe2bb:4cbfd774
-000000007d378414 08d2:0066 []    15ab8578-faae-4ebb-9827-26728be78476:0000000052de5aac:06202f405c60726d:8ad4911a
-000000008c3615d8 3868:5f66 []    8f47568c-a383-4910-83c9-36b75ac66440:0000000067faf572:750d567f3dd0c5bf:5ea938fe
-0000000090be2a77 7f32:2ca4 []    8f47568c-a383-4910-83c9-36b75ac66440:000000005912be62:47ac0c7bb89013f1:dff13db9
-00000000a7ca8e58 360f:5763 []    a9f5e129-e260-4a0e-a763-c6e3ef7b3eb6:0000000030bff255:37c8226225c804ba:665f261f
-00000000f1000713 5079:46bd []    30af7f48-15ae-4ccb-81c9-4662ad74be92:0000000014d408e3:56a9dec63aed4d8f:0f2a44ec
-000000017e3ca989 56ac:062b []    30af7f48-15ae-4ccb-81c9-4662ad74be92:000000000a8926a1:0bd54c769871aa78:b8e61d77
---------------------------------------- hit any key to continue or 'q' to quit -----------------------------------------
-root@test15 ci> scan -b 2e15cb9f62fd22ab -e 2e15cb9f62fd22ab
-2e15cb9f62fd22ab 1fc1:1486 []    2db1de18-cd37-407d-b060-481a0a214c90:000000002b1c8da1:53a9e4ba97e4a6e0:4a8bd624
-root@test15 ci> scan -b 53a9e4ba97e4a6e0 -e 53a9e4ba97e4a6e0
-53a9e4ba97e4a6e0 37f3:33a2 []    2db1de18-cd37-407d-b060-481a0a214c90:000000002b0d4b61:1c16a4ae1bef9f1f:f03c869b
-root@test15 ci> scan -b 1c16a4ae1bef9f1f -e 1c16a4ae1bef9f1f
-1c16a4ae1bef9f1f 07c8:7cd3 []    2db1de18-cd37-407d-b060-481a0a214c90:000000002afe0921:2e3ec09a8d2fdf52:8b82be48
-
      -
      - -
      - - - - - -
      -
      -
      - -