Feature Branches

This section documents Ozone's usage of git feature branches for development off of the master branch.

📄️Overview

Feature branches are used for larger or longer-running work that would be hard to land incrementally on master without destabilizing it. Feature branches are often named after the Jira epic tracking the work and an abbreviated feature name, for example HDDS-3816-ec or HDDS-10611-mpu. You can see all the Ozone repo's branches here. Most incremental changes do not require feature branches and can go directly to master as a pull request as documented in CONTRIBUTING.md.

📄️Feature Branch Merge Checklist

This section collects generic questions which can be checked for each feature branch. Some of them are obvious for some branches (for example: the decommissioning feature didn't change the s3 interface) but it's good to go through them for each of the merges. Answering these questions will also help the community to test the branch. If you have any new idea about what should be checked, submit a pull request to the ozone-site repo to update this page.

🗃Merged Feature Branches

16 items