incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Incubator Wiki] Update of "DistributionGuidelines" by myrle
Date Sat, 09 Feb 2019 09:59:21 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The "DistributionGuidelines" page has been changed by myrle:

Added motivation section to intro

   * Where possible these artefacts should not be referred to as releases.
  If any podling is found not to comply they will be asked to fix it, if a fix doesn’t happen
with a week they will be asked to remove the offending artefact(s), if a podling commits serial
offences or fails to remove artefacts when asked to within a week they will be banned from
using that distribution mechanism altogether. The IPMC reserves the right to ask INFRA to
remove the artifact if the podling doesn't follow these guidelines.
+ == Motivation ==
+ The ASF is responsible for providing software which can be used in accordance with our license.
 Code or artefacts built from code without clean IP can mean that code that doesn't belong
to us slips into users projects.  This would expose our users and the ASF to the risk of lawsuite.
 One purpose of the incubating process and its release process is to ensure that our users
can trust our projects.  Releasing artefacts built from code that hasn't been approved by
the IPMC circumvents this process.  It robs the PPMC of learning opportunities.  It increases
the likelihood that we might accidentally betray the trust of our users.
+ At the same time binary artefacts on automated distribution platforms are important to our
users for a wide variety of reasons.  This policy is intended to balance these priorities.
 If you believe you have a case in which this policy is inadequate to your situation please
bring this to our attention by mailing either or
  == GitHub ==

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message