Releases: What are contributors responsible for
0 likes•160 views
The document discusses the responsibilities of contributors for software releases. It states that contributors should file issues on GitHub for new features and use Bugzilla to report bugs. It emphasizes that documentation, testing, reviews, and tracking bugs in the release process are important responsibilities. Contributors are encouraged to discuss ideas first, design features, write code and documentation, and thoroughly test their work before seeking reviews.
Releases: What are contributors responsible for
- 1. Releases: What are contributors responsible for Shyamsundar Ranganathan Release Owner (at times)
- 2. QUIZ Time! Are you at the 2017 Gluster summit? (YES/NO) YES
- 3. QUIZ Time! Do features for Gluster need a github issue? (YES/NO) YES
- 4. QUIZ Time! Documentation is a useful practice? (YES/NO) YES
- 5. QUIZ Time! Bugs found early reduces stress later? (YES/NO) YES
- 6. QUIZ Time! Do you love stress? (YES/NO) NO
- 7. QUIZ Time! Reviews are useful? (YES/NO) YES
- 8. QUIZ Time! Bugzilla is great!? (YES/NO) You do not have to answer that!
- 10. Intent reminder for features â—Ź Github (first) â—‹ Have an idea! â—‹ Had a discussion that generated an idea? â—‹ Worked on a bug that can be bettered with a feature? â—‹ Or, plain and simple, someone told you to do something next Post it on github! â—Ź Design -> document it! â—Ź Code â—Ź Documentation -> write it! â—Ź Review â—Ź Test -> write it thoroughly!
- 11. Intent reminder for bugs â—Ź Anything not a feature, that needs to be fixed, is a bug (Duh!) â—‹ These things do include documentation, tests and other such deliverables not just code â—Ź Bugzilla â—Ź Tests -> write it! â—Ź Backports â—‹ Cloning bugs (yuck! yes I agree, but would love to hear alternatives) â—‹ Reminder: Every bug does not need a backport! â—Ź The bugzilla release tracker
- 12. Review love! ● It’s a 2-way street ○ Getting it ○ Providing it
- 13. Questions?