We are close to starting the graduation process. But I think we need give the project more time to demonstrate the ability to
Create an Apache Release AOO 3.4 is an real achievement. But the major issue it solved are due to legal concerns. It has improvement in SVG just because we are lucky to have Armin with us. It is still early to say that the project is ready to get to next release. We need at least Close a couple of new feature cycles. Propose and discuss about new features -> spec review -> design review -> implementation -> QE sign off See a steady defect fix rate. Create an Open and Diverse community We need more committers. There still no committer from C2SC. On Tue, May 29, 2012 at 2:10 AM, Rob Weir <robw...@apache.org> wrote: > I'd like to start the graduation process, with the aim of being a TLP > in time for the 3.4.1 release. > > The IPMC has a "Guide to Successful Graduation" page with a lot of > detail and advice: http://incubator.apache.org/guides/graduation.html > > The calendar here is especially useful: > http://incubator.apache.org/guides/graduation.html#toplevel > > It shows 4 steps: > > 1) a vote on ooo-dev (a community vote) on whether we want to graduate now > > 2) a discussion on ooo-dev leading to the draft of a charter for the new TLP > > 3) an IPMC vote on whether or not to recommend the podling for graduation > > 4) a vote by the ASF Board on a resolution creating the new TLP > > This thread is just a proposal. It is not the actual vote called for > in #1 above. But I'd like to gauge current sentiment. Are we all +1 > for going ahead? If not, please list what pre-graduation tasks you > believe need to be done first. > > Thanks! > > -Rob
