[ https://issues.apache.org/jira/browse/THRIFT-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701150#action_12701150 ]
Greg Stein commented on THRIFT-439: ----------------------------------- I'm with Doug on what to put into the version on trunk (eg. "0.2-dev"). We do this in the Subversion project to distinguish source trees (via checkout or a tarball) from the True Releases. The /branches/0.1.x naing is also typical. The svn Release Manager will then make a copy of the branch into /tags/0.1.0 on his local machine, edit the version information to read "0.1.0", and then commit that. This prevents "release-looking" revisions from occurring on the (0.1.x development) branch. There is no given ASF policy for the Contributors file. That is really a local social/community norm rather than a general policy. Personally, I find such a file hard to maintain, and just refer people to commit messages and Jira activity to find out more about participation. In Subversion, we have a COMMITTERS file which tracks "who has commit, and if partial only, then to which directories." That is administrative rather than advertising participation. Our log messages say things like "Patch by: John Doe <j...@example.com>" in order to provide proper credit to contributors. <very-IMO-here> To some extent, I would liken CONTRIBUTORS to @author tags. If we really want the code to be community-owned, then I believe reduction of personal credit is the best approach. </very-IMO-here> > Release 0.1 > ----------- > > Key: THRIFT-439 > URL: https://issues.apache.org/jira/browse/THRIFT-439 > Project: Thrift > Issue Type: Task > Components: Compiler (C#), Compiler (C++), Compiler (Cocoa), > Compiler (Erlang), Compiler (General), Compiler (Haskell), Compiler (Java), > Compiler (Perl), Compiler (PHP), Compiler (Python), Compiler (Ruby), Library > (C#), Library (C++), Library (Cocoa), Library (Erlang), Library (Haskell), > Library (Java), Library (Perl), Library (PHP), Library (Python), Library > (Ruby), Test Suite > Affects Versions: 0.1 > Reporter: Kevin Clark > Priority: Blocker > Fix For: 0.1 > > > This ticket is to handle all the release management stuff we've got to deal > with to do an Apache incubator release. It's our last ticket for 0.1. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.