Proposed agenda for our June 27 weekly project meeting:
- Status check for 3.4.1.
- Discuss potential timelines for 3.5. This includes picking a date for a 3.5 feature/task scope session. Next week is Independence Day in the U.S., so I am thinking July 11.
- Discuss other 3.5 goals, aside from features/tasks. What are things that need early attention, which we can begin to address now? Who wants to spearhead X, Y, or Z this cycle? (Where possibilities could include targeted enhancements, a new API for X, performance profiling of Y, unit tests for Z, etc.) We already have a lot of tickets in report/6 and there are a lot of tickets flagged for 3.5-early attention, so now is the time to step up.
While we won’t be finalizing our 3.5 plans this meeting, no time like the present to start following if you want to contribute this cycle. 20:00 UTC.
Japh 3:24 am on June 27, 2012 Permalink
Looking forward to this one. Thanks for the early post, Nacin
Peter Westwood 4:35 pm on June 27, 2012 Permalink
I’m not going to make this weeks meeting but I think that we should focus now on the things that get missed too often like triaging trac and going through the 3.5-early tickets and the bug fix ones with patches on them to review, commit/feedback so that we can benefit from these contributions.
That gives us a clear focus for now while we discuss the 3.5 feature ideas.
Andrew Nacin 4:36 pm on June 27, 2012 Permalink
Seems like we’re on the same page. You just said it better.