Hibari v0.3.0 Release #30

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

Comments

Projects
None yet
1 participant
@tatsuya6502
Member

tatsuya6502 commented Mar 4, 2013

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

@ghost ghost assigned tatsuya6502 Mar 4, 2013

@tatsuya6502

This comment has been minimized.

Show comment
Hide comment
@tatsuya6502

tatsuya6502 Mar 4, 2013

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

Member

tatsuya6502 commented Mar 4, 2013

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

This comment has been minimized.

Show comment
Hide comment
@tatsuya6502

tatsuya6502 Mar 9, 2013

Member

Step 8. Change XDIST from dev to master(?) in Makefile:

XDIST?=dev

Member

tatsuya6502 commented Mar 9, 2013

Step 8. Change XDIST from dev to master(?) in Makefile:

XDIST?=dev

@tatsuya6502

This comment has been minimized.

Show comment
Hide comment
@tatsuya6502

tatsuya6502 Mar 9, 2013

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.

Member

tatsuya6502 commented Mar 9, 2013

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

This comment has been minimized.

Show comment
Hide comment
@tatsuya6502

tatsuya6502 Mar 16, 2013

Member

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

Remaining dev tasks:

Member

tatsuya6502 commented Mar 16, 2013

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

Remaining dev tasks:

@tatsuya6502

This comment has been minimized.

Show comment
Hide comment
@tatsuya6502

tatsuya6502 Mar 22, 2013

Member

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

Member

tatsuya6502 commented Mar 22, 2013

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

@tatsuya6502

This comment has been minimized.

Show comment
Hide comment
@tatsuya6502

tatsuya6502 Mar 22, 2013

Member

Remaining dev tasks:

Member

tatsuya6502 commented Mar 22, 2013

Remaining dev tasks:

@tatsuya6502

This comment has been minimized.

Show comment
Hide comment
@tatsuya6502

tatsuya6502 Mar 22, 2013

Member

Step 2. Update the release note

Completed: efb8ed1

Member

tatsuya6502 commented Mar 22, 2013

Step 2. Update the release note

Completed: efb8ed1

@tatsuya6502

This comment has been minimized.

Show comment
Hide comment
@tatsuya6502

tatsuya6502 Mar 23, 2013

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
Member

tatsuya6502 commented Mar 23, 2013

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

This comment has been minimized.

Show comment
Hide comment
@tatsuya6502

tatsuya6502 Mar 23, 2013

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"
Member

tatsuya6502 commented Mar 23, 2013

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

This comment has been minimized.

Show comment
Hide comment
@tatsuya6502

tatsuya6502 Mar 26, 2013

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).

Member

tatsuya6502 commented Mar 26, 2013

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

This comment has been minimized.

Show comment
Hide comment
@tatsuya6502

tatsuya6502 Apr 4, 2013

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.

Member

tatsuya6502 commented Apr 4, 2013

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