You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by Dan Sully <da...@electricrain.com> on 2009/03/02 15:33:52 UTC

Re: How, and if, to continue using and supporting Thrift

* Kevin Clark shaped the electrons to say...

>I hear you. The situation is frustrating, I agree. I'm happy to push
>code (and have been doing my best to keep up with the Ruby queue with
>Bryan), but I'm not a Python guy. David and Ben generally took care of
>those. I've pinged David about THRIFT-148, and expect he'll pipe up on
>the list.

Another +1 for integrating the Twisted patches.

>As for releases, I'm still all for doing a real release by March as
>we'd discussed recently. I'm not sure what sort of support is needed
>to get us there, but I'm happy to give it.

Agreed. Does there need to be a milestone date set at the Apache Incubator level
for this? 

-D
--
<dsully> please describe web 2.0 to me in 2 sentences or less.
<jwb> you make all the content. they keep all the revenue.

Re: How, and if, to continue using and supporting Thrift

Posted by Jérémie BORDIER <ah...@gmail.com>.
On Mon, Mar 2, 2009 at 11:17 PM, Esteve Fernandez <es...@sindominio.net> wrote:
> On Monday 02 March 2009 22:08:19 Doug Cutting wrote:
>> Many projects maintain a page describing the details of their particular
>> release process.  Some examples are:
>>
>> http://httpd.apache.org/dev/release.html
>> http://wiki.apache.org/hadoop/HowToRelease
>>
>> Perhaps someone could start drafting something like this for
>> Thrift?
>
> I sent a very simple roadmap of what I thought should be done in order to
> release a new version, in the hopes that more people would expand it. Sadly,
> it didn't get much attention and I don't know if anybody else is motivated to
> roll a release:
>
> http://mail-archives.apache.org/mod_mbox/incubator-thrift-dev/200902.mbox/%3C200902031844.51434.esteve@sindominio.net%3E
> http://mail-archives.apache.org/mod_mbox/incubator-thrift-dev/200902.mbox/%3C200902071056.40620.esteve@sindominio.net%3E
>
> I even tried (without success) to stoke the fire by starting a commit/bug
> squashing fest and keeping people motivated, but I don't think I'm qualified
> to officially organize anything or tell anyone what to do.
>
> Sorry if I sound too pessimistic and/or whiny, but after reviewing issues and
> sending patches for them that didn't even affect me (I'm interested in
> Python, but have contributed to C++, Perl, C#, Ruby, etc. anyway), and seeing
> that they're not only not being committed, but not being discussed at all,
> I'm becoming less and less motivated to contribute. I'm not asking them to be
> automatically committed, but at least, some discussion (and criticism!)
> around them would be great.
>
> Cheers.
>

Hi Esteve,

I'm not a big commiter as you are, but i still fixed some bugs and
started nice enhancement to thrift, some that were submitted but never
applied, and some that i finally never finished due to the lack of
motivation going around here... I'm so disappointed to see how hard it
is to get something committed on Thrift while there are dozens of
official contributors and tons of commits each day on a huge project
like VLC. How the hell could a little project like thrift grow up with
a so slow and limited contribution model ? Seriously...

I totally get your point and +1 your reaction.

Cheers,
Jérémie

Re: How, and if, to continue using and supporting Thrift

Posted by Esteve Fernandez <es...@sindominio.net>.
On Monday 02 March 2009 22:08:19 Doug Cutting wrote:
> Many projects maintain a page describing the details of their particular
> release process.  Some examples are:
>
> http://httpd.apache.org/dev/release.html
> http://wiki.apache.org/hadoop/HowToRelease
>
> Perhaps someone could start drafting something like this for
> Thrift?

I sent a very simple roadmap of what I thought should be done in order to 
release a new version, in the hopes that more people would expand it. Sadly, 
it didn't get much attention and I don't know if anybody else is motivated to 
roll a release:

http://mail-archives.apache.org/mod_mbox/incubator-thrift-dev/200902.mbox/%3C200902031844.51434.esteve@sindominio.net%3E
http://mail-archives.apache.org/mod_mbox/incubator-thrift-dev/200902.mbox/%3C200902071056.40620.esteve@sindominio.net%3E

I even tried (without success) to stoke the fire by starting a commit/bug 
squashing fest and keeping people motivated, but I don't think I'm qualified 
to officially organize anything or tell anyone what to do.

Sorry if I sound too pessimistic and/or whiny, but after reviewing issues and 
sending patches for them that didn't even affect me (I'm interested in 
Python, but have contributed to C++, Perl, C#, Ruby, etc. anyway), and seeing 
that they're not only not being committed, but not being discussed at all, 
I'm becoming less and less motivated to contribute. I'm not asking them to be 
automatically committed, but at least, some discussion (and criticism!) 
around them would be great.

Cheers.

Re: How, and if, to continue using and supporting Thrift

Posted by Doug Cutting <cu...@apache.org>.
Dan Sully wrote:
> Does there need to be a milestone date set at the Apache 
> Incubator level
> for this?

No.

Making a release is a primary act of an Apache project.  Successful 
execution of a release process is perhaps the biggest milestone towards 
graduation from the Incubator.

The project should perform this process mostly on its own, with advice 
from its mentors.  There's ample documentation, e.g.:

http://www.apache.org/dev/index.html#releases
http://incubator.apache.org/guides/releasemanagement.html

Many projects maintain a page describing the details of their particular 
release process.  Some examples are:

http://httpd.apache.org/dev/release.html
http://wiki.apache.org/hadoop/HowToRelease

Perhaps someone could start drafting something like this for
Thrift?

Doug