www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig L Russell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LEGAL-438) Github release pages showing unapproved releases
Date Sun, 17 Feb 2019 23:46:00 GMT

    [ https://issues.apache.org/jira/browse/LEGAL-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16770697#comment-16770697
] 

Craig L Russell commented on LEGAL-438:
---------------------------------------

[~rvs] I agree.

We at Apache have a very legal definition of what a release is, how it is an official act
of the Foundation, needs to be voted, etc. etc.

At github, a release is just a collection of bits that a project has decided will not burn
down your computer if you install it.

The difference in terminology has already hurt a few projects and I would second Roman's ask
for infra to take the lead in sorting it.

> Github release pages showing unapproved releases
> ------------------------------------------------
>
>                 Key: LEGAL-438
>                 URL: https://issues.apache.org/jira/browse/LEGAL-438
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Justin Mclean
>            Priority: Major
>
> The IPMC is trying to provide advice to podlings on how to handle releases listed on
GitHub release page .e.g [https://github.com/apache/incubator-doris/releases]
> For releases that occurred before incubation it seems best to label them as non Apache
release so that's OK.
> However GitHub will turn any git tag into a release that means that release candidates
and the like will show up on this release page (see example above) be marked as a release
and be available to download as a .tar.gz or .zip to the general public. This doesn't seem
in line with ASF release and distribution policies. [1][2]
> What do we do about this?
>  a) Ignore that they show up here.
>  b) Mark all release / tags as "pre-releases" (another GitHub release feature)
>  c) Delete RC tags after they have been voted on?
>  d) Disable release pages in GitHub
>  e) Something else?
> This issue has been raised to GitHub some time back and there's little action on it.
[3]
> Note that TLP also have the same issue.
> 1.[http://www.apache.org/legal/release-policy.html#publication
>  ]2.[https://www.apache.org/dev/release-distribution.html#unreleased
>  3|https://www.apache.org/dev/release-distribution.html#unreleased].[https://github.community/t5/How-to-use-Git-and-GitHub/Tag-without-release/td-p/6255]
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


Mime
View raw message