You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by "Henri Yandell (JIRA)" <ji...@apache.org> on 2009/07/17 08:54:14 UTC
[jira] Commented: (LEGAL-34) Release VOTE and svn tag, source
package, binary package
[ https://issues.apache.org/jira/browse/LEGAL-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732378#action_12732378 ]
Henri Yandell commented on LEGAL-34:
------------------------------------
I'm not sure there's much here with a Legal PMC context. Admittedly we don't have anyone who is in charge of this policy, which would make it a question for the board imo. I seem to recall this came up there, but not whether it reached any conclusion.
My opinion:
Votes are on all of the files in that release, and I would not expect a vote to get off the ground if an SVN tag did not exist. A release vote is 3 +1s from the PMC and majority (or whatever the official statement is).
Repackaging a release is also subject to a vote, however a PMC can choose how that vote is done. If a PMC want to consider that maven jars are released subsequent to the original release, and that that vote can be lazy consensus over 1 day, then I've no problem. I would consider a PMC who are happy for an RM to push out a repackage without it having at least been made available for others to look at it a stupid PMC.
I consider repackaging to be changing the collective nature of the package - ie: taking some of the files and putting them in a zip (aka jar); but not to include modifying the release.
> Release VOTE and svn tag, source package, binary package
> --------------------------------------------------------
>
> Key: LEGAL-34
> URL: https://issues.apache.org/jira/browse/LEGAL-34
> Project: Legal Discuss
> Issue Type: Question
> Reporter: Stefano Bagnara
>
> I saw various practices in the ASF about the release vote.
> A. Some PMC vote svn tags and then a release is made and then the src and binary packages generated are not voted before publishing.
> B. Some PMC vote on a source package created from the svn tag and then any other binary package created from that source is published without a vote.
> C. Some PMC vote all of the published content.
> Is there any ASF policy we should be aware before each PMC can decide how to deal with release vote?
> Here is what I found in ASF pages.
> http://www.apache.org/dev/release.html
> ---
> The Apache Software Foundation produces open source software. All releases are in the form of the source materials needed to make changes to the software being released. In some cases, binary/bytecode packages are also produced as a convenience to users that might not have the appropriate tools to build a compiled version of the source. In all such cases, the binary/bytecode package must have the same version number as the source release and may only add binary/bytecode files that are the result of compiling that version of the source code release.
> ---
> Sub-issue: is it ok for a project to publish on www.apache.org/dist an installer created by one contributor based on the released sources and using a commercial installer tool ? Does this require a VOTE ?
> http://markmail.org/message/5agseuhdoyu3fh2x
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org