-
Notifications
You must be signed in to change notification settings - Fork 32
Project Branches
Samantha Chan edited this page Jul 6, 2016
·
9 revisions
There are two types of branches in the Messaging Toolkit:
- Active Branch - This is a branch where active development is done. New features and enhancements can be added to this branch.
- Maintenance Branch - A maintenance branch for building maintenance releases for the toolkit. No new features or enhancements can be made to the maintenance branch. Maintenance branch is named with a "_m" postfix in the branch name to indicate that the branch is for maintenance. Only critical customer fixes can be delivered to this branch. If a fix is required to be made to the maintenance branch, the fix needs to goes through a review process:
- Contributor / Committer creates a fix for the customer problem.
- The contributor asks another committer to review the fix, to ensure the the fix is properly tested and implemented.
- If the fix is good, the reviewer will add a +1 vote.
- A fix cannot be delivered to the maintenance branch without a +1 vote from another committer.
Current Active Branches:
- Master - targeted for next IBM Streams major release
- Toolkit Version: Version 5.0.x
- Minimum Streams Version: Streams 4.1.0 and up
- Kafka 0.9, Governance, CC
- 4.0.x - feature branch to support Kafka 0.9 server/RabbitMQ/Message Hub
- Toolkit Version: Version 4.0.x
- Minimum Streams Version: Streams 4.0.0 and up
- Note: We have to bump the version number of this toolkit from 2.0 to 4.0 due to breaking changes in the Kafka operator.
- Kafka 0.9, No Governance, CC
Maintenance Branches
- 3.0.x_m - targeted for future maintenance releases of IBM Streams 4.1.x.x
- Toolkit Version: Version 3.0.x
- Minimum Streams Version IBM Streams 4.1.x.
- Kafka 0.8, Governance and CC
- 2.0.x_m - targeted for future maintenance releases of IBM Streams 4.0.x.x
- Toolkit Version: Version 2.0.x
- Minimum Streams Version: IBM Streams 4.0.x
- Kakfa 0.8, No Governance, No CC