Friday's Plone Tune-Up to Focus on Plone 3.3.6 Release Blockers
This week's Tune-Up will focus on finishing the 3.3.6 release. We will focus on fixing the last tests so that this release can move forward.
Plone Tune-Ups are regularly-scheduled one-day mini-sprints where members of the Plone Community from around the globe come together online to grab some outstanding tickets from the Plone Trac system and help move Plone forward.
Plone 3 release manager Alan Hoey has tagged some of the important test-related issues which are holding up the release of 3.3.6 so that those in the tuneup can work on resolving them. If you're a developer and have time to spend Friday, we hope you will drop in and help us get Plone 3.3.6 out the door.
Tune-Ups offer an excellent environment for new developers to get started with Plone development and understand the process used by the community for identifying, tracking, and resolving issues with Plone. Development experts from the community are available online during these events to provide help and answer questions. Tune-Ups also offer structured time where established developers can spend a couple of hours picking out and resolving important tickets. Tickets for each Tune-Up are tagged as to level of difficulty and relative time needed to resolve them, making choosing the right tickets to work on a straightforward process.
The Plone Tune-Up is a great way to give back to the Plone community. Not everyone wants to be a core developer or maintain a product in Plone, but most people have the ability to squash a few bugs, provide QA or work on documentation. Every time you give time back to the community you make Plone a better solution for everyone.
You can find out all about Plone Tune-Ups by visiting the Plone Tune-Up Network, which will provide all the information you need to get started with this important work.