Weekly Development Planning

June 27, 2016

1. Next generation items
2. 3 Pull requests resolution (Sheehan)
3. Close issues

June 20, 2016

1. Release v0.5-developer-preview
2. Release procedure
3. Discuss PR resolution: Suggested to use part of this meeting and mid-weed slack channel to resolve PRs (5 at a time)
4. Discuss new ideas: Use the emailing list hyperledger-fabric@lists.hyperledger.org to start the discussion; if can't resolve, we'll add it to the Monday agenda as appropriate
5. Need a list of component experts so that the community can contact for help

June 13, 2016

1. Release logistical exercise (by 6/17, end of hackathon)

   • Create a release branch to allow bug fixes
   • Suggested release branch name as a name of circulating currencies
   • Master branch is the latest greatest
   • Available as docker images
   • A Fabric wiki describing the release and linked from the main README.md
   • *** I discussed more with Ramesh, Trevor, and Ry today 6/14 and learned that the CI should work agaist the release branch; we just need to target the selected PRs to the release branch (not the master branch). They recommend to merge from commits the release branch to the master branch often. I will write a release process

2. Pull requests review

   • Enhancement to existing code requires some discussion (issue+slack) to reduce review effort
   • We need everyone (expert in area) to help review the pull requests

3. Virtual Hyperledger Hackathon 6/15 - 6/17

   • Coverage Tests (unit and behave), bug fixes, and triage on the issues (more than 300)
   • Many modules have no or little coverage (to find current coverage, run make unit-test)
   • Tools: Go test, Ginkgo&Gomega, Behave, others?
   • Fabric hackathon channel