5

Community Release Manager

Rushabh Mehta edited this page 2019-01-03 12:53:23 +05:30

Table of Contents

• Introduction
• Regular Release
• Contribution Review
• Severe Bug Monitoring
• Monitoring of Security Reports and Notifications

Introduction

The role of the community release manager is to ensure that regular, high quality releases happen in time and the install and update process of bench is does not break based for the community. The role is also to keep updating the contribution guidelines and help review and manage open pull requests from a guidelines point of view.

Regular Release

Regular release should happen on a Tuesday. The release process should include:

1. Preparing release notes.
2. Manual / automated testing based on the Standard Release Test Plan (SRTP).
3. Manually test new contributions / update.
4. Ensure all tests are passing.
5. Announcing the release with the release notes on the forum.
6. Maintain, automate and update the SRTP.
7. Manager release for frappe, erpnext and bench repos (if required)

Contribution Review

1. Review open contributions for consistency with Contribution Guidelines.
2. Tag, close contributions that are very far from the standard.

Severe Bug Monitoring

1. Monitor severe bug reports on forum and GitHub.
2. Severe bugs include bugs that make the system unusable, or failure to install or upgrade.
3. Work with module maintainers to fix and make an urgent release if required.

Monitoring of Security Reports and Notifications

1. Monitor security reports.
2. Work with module maintainers to fix security reports.
3. Maintain registry of security fixes.
4. Notify on the forum / website after quarantine period.