2.1.x Community Update and Planning BOF

Why a BOF?

Hey, All:

The Conference Committee didn't think that a 2.1.x update/planning roundtable should be a presentation, so it will be a BOF at this conference.

Please feel free to edit this page to add your suggestions on what we should talk about. I'm not entirely sure how we'll prioritize issues; maybe we'll aim for a BOF early in the week where we'll start by prioritizing by voting, and then if we need another one we'll schedule it?

Let me know what you think, or add a section to the page with ideas!

Thanks,

Brian

Suggested Topics (in the order that I thought of them)

• general workflow improvements
• locally tested patches
• should we release 2.1.3 before moving to untested patches?
• patches that have not been tested locally
• 2.1.x test server(s) – mysql now up, oracle has been offered
• if we move to untested patches, how do we treat the repo and will this require regular 2.1 releases?
• discussion of any important patches that one or more members of the group want to tackle
• discussion of any 2.2/2.3/2.4 features that one or more members of the group want to tackle/backport