[jira] [Commented] (LEGAL-621) Is advising the end-users to patch from main or unreleased code ok?

["Sean R. Owen (Jira)" <ji...@apache.org>]

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

Sean R. Owen commented on LEGAL-621:
------------------------------------

This just seems like useful information for developers, who may be operating on unreleased source code in the course of developing. It hardly seems to qualify as publishing unreleased artifacts; it's information about working with artifacts before release. Spark does this for sure https://spark.apache.org/developer-tools.html

> Is advising the end-users to patch from main or unreleased code ok?
> -------------------------------------------------------------------
>
>                 Key: LEGAL-621
>                 URL: https://issues.apache.org/jira/browse/LEGAL-621
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Jarek Potiuk
>            Priority: Major
>
> Hello Here,
> We had a discussion in Airlfow about whether we can add a description to the "end-user" documentation hosted at "http://airflow.apache.org/docs" to patch certain problems using unreleased yet code (commits from main/PRs that have not yet made it into any official release).
> The PR we discussed it is here: [https://github.com/apache/airflow/pull/26759]
> We basically wanted to add a chaptaer similar to one quoted below.
> My opinion is that we should not make it part of the "http://airlfow.apache.org/docs" (which is intended to be an end-user documentation, but rather than that we could make it a README of sorts in the GitHub repository and point to it from the documentation that is in the repo/GitHub rather than from "end-user" docs.
> I am basing my thinking on 
> [https://www.apache.org/legal/release-policy.html#publication]
> ??Projects SHALL publish official releases and SHALL NOT publish unreleased materials outside the development community.??
> ??During the process of developing software and preparing a release, various packages are made available to the development community for testing purposes. Projects MUST direct outsiders towards official releases rather than raw source repositories, nightly builds, snapshots, release candidates, or any other similar packages. Projects SHOULD make available developer resources to support individuals actively participating in development or following the dev list and thus aware of the conditions placed on unreleased materials.??
>  
> Here is the text we wanted to add:
> ------
> Applying patches from ``main``
> ==============================
> On occasion, you may want to apply fixes from ``main`` which have not yet made it into a release.  The following example shows how you can apply a patch from a PR.
>  
> {{{{   FROM apache/airflow:2.4.0-python3.8}}}}
> {{{{    USER root}}}}
> {{{{    RUN apt-get update && apt-get install -y patch patchutils}}}}
> {{        RUN set -ex; }}}}
> {{          curl -o /tmp/12345.patch [https://patch-diff.githubusercontent.com/raw/apache/airflow/pull/12345.patch]; }}
> {{         cd /home/airflow/.local/lib/python3.8/site-packages/airflow;}}
> {{         filterdiff -p1 -i 'airflow*' /tmp/12345.patch | patch -u -p 2; }}
> {{{{        rm /tmp/12345.patch}}}}
> {{{{    USER airflow}}}}
> The process to apply a patch from a commit or a range of commits is similar. For example you can get a patch of the changes in commit ``6b7eb5`` with ``[https://github.com/apache/airflow/commit/6b7eb5caebc63dfa2ee3609a4c400d502f0894fd.patch]``
> -----
>  
> Am I too "strict" in my thinking/opinion ? Is that OK to refer those kind of instructions in the end-user's documentation?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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