Skip to content

Hibari v0.3.0 Release #30

Open
tatsuya6502 opened this Issue Mar 4, 2013 · 11 comments

1 participant

@tatsuya6502
Hibari member

Target Date

March 18th or 25th, 2013

Steps

  1. Update dialyzer warnings for Erlang/OTP R15B03-1. (Not R16B)
  2. Update the release note
  3. In each sub project with some commits, update the version number on dev branch, marge dev branch to master branch, and tag the merge commit.
    • gdss-admin v0.3.0
    • gdss-brick v0.3.0
    • gdss-client v0.3.0
    • gdss-ubf-proto v0.3.0
    • cluster-info v0.3.0
    • partition-detector v0.3.0
    • congestion-watcher v0.3.0
    • gmt-util v0.3.0
  4. Create and test release candidates (RCs)
  5. In the main project, update the version number on dev branch, marge dev branch to master branch, and tag the merge commit.
    • hibari v0.3.0
@tatsuya6502 tatsuya6502 was assigned Mar 4, 2013
@tatsuya6502
Hibari member

Steps (continued)

Step 6. Merge dev branch of hibari-dec to master branch, and tag the merge commit.
Step 7. Update Hibari Documents on the web

@tatsuya6502 tatsuya6502 closed this Mar 4, 2013
@tatsuya6502 tatsuya6502 reopened this Mar 4, 2013
@tatsuya6502
Hibari member
@tatsuya6502
Hibari member

Step '1. Update dialyzer warnings for Erlang/OTP R15B03-1. (Not R16B)

Done with this task. Commit: 2df90ed

Since dialyzer options -Werror_handling and -Wunderspecs are just added, dialyzer now produces more warnings than before. I'll open a separate GitHub issue to track it.

@tatsuya6502
Hibari member

Push the release target date to Thu, Mar 28th.

Remaining dev tasks:

@tatsuya6502
Hibari member

Created a wiki page Release Procedure at https://github.com/hibari/hibari/wiki/Release-Procedure

@tatsuya6502
Hibari member

Remaining dev tasks:

@tatsuya6502
Hibari member

Step 2. Update the release note

Completed: efb8ed1

@tatsuya6502
Hibari member

Done with the following tasks:

https://github.com/hibari/hibari/wiki/Release-Procedure#update-dev-branches

Update Dev Branches

  1. hibari/dev - Check dialyzer warnings
  2. hibari/dev - Verify that the release note is up-to-date
  3. sub-project/dev - Update the version number in src/*.app.src
  4. hibari/dev - Update deps version numbers in rebar.config
  5. hibari/dev - Run make check-package once again

Versions:

  • gdss-admin v0.3.0
  • gdss-brick v0.3.0
  • gdss-client v0.3.0
  • gdss-ubf-proto v0.3.0
  • cluster-info v0.3.0
  • partition-detector v0.3.0
  • congestion-watcher v0.3.0
  • gmt-util v0.3.0
  • ubf-thrift v1.6.1-hibari02
@tatsuya6502
Hibari member

Done with the following tasks:

https://github.com/hibari/hibari/wiki/Release-Procedure#update-dev-branches

For a Major Release, Create Release Branch

  1. sub-project/dev - Create release branch release-x.y from dev branch
  2. hibari/dev - Create release branch release-x.y from dev branch
  3. hibari/rc - Change XDIST from "dev" to "rc" in Makefile
  4. manifests/dev - Create release branch release-x.y from dev branch
  5. manifests/rc - Set revision="release-x.y"
@tatsuya6502
Hibari member

Testing Hibari v0.3.0 RC, so far so good:

  • All eunit tests passed as usual.
  • Two QuickCheck tests are failing (since v0.1.x)
    • I filed GitHub issues for them. I'll try to address them after v0.3.0 release.
  • Ran a couple of 8-hour stability tests on SmartOS with the following conditions. Found no issue:
    • 4-node Hibari cluster (3 admins) with chain length 3
    • SmartOS base64 1.9.1, package repo: 2012Q4 x86_64
    • Erlang/OTP R15B02, from the package repo
    • DTrace tracepoints enabled, run some D scripts
    • syncwrites = true
    • Basho Bench workload similar to hibari-native.config but altered as {concurrent, 50} and {mode, {rate, 10}}
    • Perform checkpoint and run scavenger

I'm going to run the same stability test on CentOS 6.4 (x86_64).

@tatsuya6502
Hibari member

I had to postpone v0.3.0 release to sometime between mid and late April. There is a blocker issue with a combination of brick_simple:rename/6 and the scavenger (#33 (comment)) and I'm currently working on it.

@tatsuya6502 tatsuya6502 added the Task label Mar 29, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.