Development Team/Meetings: Difference between revisions
| Line 31: | Line 31: | ||
* How can we improve the review process? | * How can we improve the review process? | ||
** action item: unmadindu/cjb setup review board http://www.review-board.org/ | ** action item: unmadindu/cjb setup review board http://www.review-board.org/ | ||
1. Break your projects into small pieces that can be submitted for review independently. Submit for review as early as possible, by mailing list or review-board site or whatever other mechanism. | |||
More specific: | |||
* preferred way if possible: 1. code a small part, 2. submit to review, 3. get into joyride, 4. repeat | |||
* not talking about: 1. code everything, 2. split in patches, 3. submit | |||
2. If you want testing before review, make a topic build. | |||
3. Some new tools will be needed to make topic builds easier to make. (.img, .rpm, and .deb) | |||
* Bundlebuilder: how to create the source tarballs best to not incude unintentional files. | * Bundlebuilder: how to create the source tarballs best to not incude unintentional files. | ||
* How to announce a new release of an activity best? | * How to announce a new release of an activity best? | ||