On Fri, 2008-11-21 at 18:23 -0800, David Reiss wrote: > I can't speak for anyone else, but I don't feel particularly motivated > to do a release. Here at Facebook, we generally build all of our backend > software against the trunk and "release" whenever we need new features in > production. If someone wants to drive this process, I'm happy to answer > any questions about the origins or license of the code and/or apply patches, > but I don't think I'll be taking the lead. In the mean time, simply running > "make dist" gives you a pretty nice release-style tarball.
At some point, a release needs to be made as a part of the incubation process. That release (before being released) will be vetted thoroughly by the Incubator community, and having a release that successfully passes that will be a significant part of the process of moving towards graduation. Also, upon graduation, the principal responsibility of the Thrift Project Management Committee (PMC) will be to release code. Code in SVN is not considered released, only code that has been tarballed and voted on by members of the PMC. We need to have releasing as a part of the roadmap, and we'll need to have releasing as a part of what the prospective PMC offers to its users. How do we plan to move in that direction? Upayavira
