Sorry about this, I was in the same boat as Todd. Hadn't yet seen the new candidate -- it went into my gene...@incubator mail filter, which I do not check regularly due to the high volume and generally low relevance (to me, at least -- most mail is about projects I've got nothing to do with).
Time to fix up my mail filters (I wouldn't be surprised if many folks missed this thread for the same reason, of having gene...@incubator on the To line). Taking a look and voting momentarily. Generally, I've felt like we actually have gotten a good number of +1s from folks on the project quite quickly, and have spent more time waiting on getting our IPMC votes. What I have seen is a mismatch in what people are paying attention to in the votes: - project members tend to focus on compilability, code compatability/regression - IPMC focuses on legal, licensing, etc. (this is where the RCs have had blocking issues) So, I think what's happened here is since we still don't have a ton of experience releasing and lots of new files are still being added, we're lax about checking for things like license headers etc. which has resulted in more rounds of release candidate iteration than people probably expected here. As we get better I'd expect we spend less time on this stuff as we form better habits and can better anticipate what issues will likely be raised when an RC is sent out. Cheers, Mark -----Original Message----- From: Todd Lipcon [mailto:t...@cloudera.com] Sent: Monday, August 02, 2010 11:47 AM To: thrift-dev@incubator.apache.org Subject: Re: This is nonsense Hi Upayavira, The last RC I saw was 0.3.0rc5, which was +1ed by many members of the Thrift community and then voted down by the IPMC due to some legal issues. Bryan was going to roll a new rc, but I can't seem to find a vote thread for any rc6. As I understood it, we're in a holding pattern waiting for a new rc before voting again -- what am I missing? -Todd On Mon, Aug 2, 2010 at 11:40 AM, Upayavira <u...@odoko.co.uk> wrote: > Dear Thrift Community, > > Some time ago, Bryan Duxbury volunteered to be release manager for > Thrift, and has, since then, put a lot of effort into producing > releases, rolling six release candidates, each one closer to meeting the > set of legal requirements desired by the incubator. These requirements > all in place to make it as clear as possible the terms on which end > users can use the software. > > For each RC, he has submitted a vote on thrift-dev, asking for folks to > validate that both the code is good and, to the best of their knowledge, > the release is validly licensed/etc. > > These votes can be taken to show the extent to which the community is > behind a release. By community I am not limiting it to committers - > include anyone actively participating in the development of the code and > community. > > Until yesterday, Bryan's last RC has not had a single response nor vote > in five days. It still only has votes from mentors, and none from the > Thrift community. > > I can only take this as a sign that the Thrift community is either not > behind Bryan's releases, or more likely that the Thrift community is not > behind formally releasing code. > > Without cracking this release issue, Thrift will not leave the incubator > (seeing as *releasing* open source code to the public is what the ASF > exists for), and incubator is not a permanent place for projects. Thrift > needs to be setting its sights on graduating, or on moving elsewhere. > > Am I right in my assumption that the Thrift community is not interested > in releasing code? Is everyone happy just running off trunk? Am I > missing something? Do folks actually want Thrift to release code? Or > should Thrift move somewhere else and just get on with developing the > codebase as it generally does now? > > Upayavira > > > > -- Todd Lipcon Software Engineer, Cloudera
