Page History
...
If you have status items to report, please enter them below at least 1 hour before the meeting starts.
Meeting Notes
Excerpt |
---|
Reviewing how 3.0 release process went, brainstorms of 4.0 release processes, revisiting JIRA Workflow improvements |
- Getting Code Reviewed - general consensus around the following:
- developers should be encouraged to locate a reviewer themselves, if possible
- if a reviewer cannot be found or is not self-selected, that is where either the RT (during a release) or Committers in general can help to locate an appropriate reviewer. (And we all prefer that #1 happen as much as we can)
- 4.0 Release processes / scheduling features. Some general consensus/brainstorms around the following:
- We all agree it'd be best for all development to be more open in general (share code/ideas/plans early & often)
- We'd like it if we could work with contributors to schedule a time that their (larger) feature will be ready for review. (Code need not all be completed by date of first review, but should be in a reviewable state)
- We may or may not want to mess around with different "final chance" deadlines...to perhaps get the "last minute pile-up of features" to happen earlier & give the RT/Committers time to work through it. The brainstorm was that the "final chance" for large features to be submitted as a pull request could be 2 months before the "freeze".
- We may be able to combine #2 & #3 above
- Discussion of JIRA Workflow Improvements
Meeting Transcript
- Full IRC Transcript is available at - http://irclogs.duraspace.org/index.php?date=2012-12-1219
Action Items
(Action items go here, if any)
Overview
Content Tools