potiuk edited a comment on pull request #12668:
URL: https://github.com/apache/superset/pull/12668#issuecomment-766322776


   > http://www.apache.org/legal/release-policy.html#publication
   >
   > In my opinion, any documentation published on superset.apache.org should 
be considered as intended for the end-user. Documentation for contributors is 
in the repository.
   
   I must agree with @mik-laj - IMHO this is really against the release policy 
of ASF to point to master versions. The only releases you should advertise in 
public website should indeed be the released ones following the official 
release process, which involves signing the sources, voting by PMC members and 
publishing them via Apache SVN. You can still publish convenience packages 
(such as released PyPI packages) but they should be prepared using the sources 
officially published and voted on by PMC members. 
   
   Encouraging end-users to use master version by cloning the repo is very 
risky for the project and put the PMCs of the project in a difficult situation 
because they are responsible to check if the end users gets the software that 
follows all the licensing policies (this is one of the most important effect of 
the formal voting).
   
   Following the releas policy has the effect that it makes the PMC members 
idemnified of any potential litigations and ASF takes over any potential 
litigation costs etc.
   
   It has rather serious legal implication, so I suggest you discuss it within 
the PMC members  (cc: @mistercrunch since you are PMC here :) I know you have 
experience from Airflow as well so maybe you can also state your opinion here). 


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to