On Sat, Mar 25, 2017 at 11:10 AM, John D. Ament <john.d.am...@gmail.com> wrote: > On Sat, Mar 25, 2017 at 1:14 PM Mike Jumper <mike.jum...@guac-dev.org> > wrote: > >> On Sat, Mar 25, 2017 at 6:25 AM, John D. Ament <johndam...@apache.org> >> wrote: >> > >> > On Sat, Mar 25, 2017 at 1:03 AM Mike Jumper <mike.jum...@guac-dev.org> >> > wrote: >> > > ... >> > > Thanks, John. We definitely won't move forward with altering the >> presence >> > > of the ASF headers until we get a ruling from legal one way or the >> other. >> > > I'm equally worried that simply removing them would be just as wrong, >> due >> > > to the way GNU Autotools pulls in chunks of build file source verbatim. >> > > >> > > What about your other feedback regarding the draft release notes + >> > > downloads? >> > > >> > > >> > http://www.apache.org/dev/release-distribution.html#unreleased >> > >> > I feel you violate this, but since its unlinked I'm OK with sayings just >> > there. For the next release, prep the page, but don't publish it. >> > >> >> Can you clarify how this is violated? >> >> With the release artifacts themselves uploaded to staging dist prior >> to being promoted to release dist, Maven artifacts uploaded to a >> staging repository prior to being promoted to the release repo, etc., >> I'm not seeing why uploading the release notes to a staging section of >> the website would be a violation of policy. >> >> Part of the idea behind staging the release notes in this way was to >> ensure that promoting an RC to release involves only updating >> metadata, with all tangible release-related work being strictly part >> of each RC. If the release notes cannot be uploaded until the release >> is going out, then that'll be a part of the system that doesn't get >> exercised during the RC process. >> >> > Just to be 100% clear, I'm talking about this page: > http://guacamole.incubator.apache.org/releases/0.9.12-incubating/ > > Here are the items this page violates (from my POV): > > - You're linking to dist.apache.org
Is providing links to dist.apache.org not a requirement of the release process whilst those artifacts are available on dist.apache.org only? Were there no release notes on the website containing said links, wouldn't a link to dist.apache.org need to be present in the email regarding the RC vote, which ultimately reaches the same audience? If/when the RC is promoted to a release, those links no longer point to dist: http://guacamole.incubator.apache.org/release-procedures-part4/#update-website > - There's nothing stating that these files are only for the dev community > (there is a note saying its not released yet) If explicitly stating that the files are meant only for the dev community is what needs to be done, then we'll gladly do that. If it's necessary that the URL pattern of the staged notes needs to be different from the URL pattern of actual releases, that can be done as well. > - Anyone who has this link can use the prebuilt software. > But that also goes for anyone with access to git, or anyone who visits dist.apache.org, or anyone following the dev@ list ... correct? > Effectively, everything listed on > http://www.apache.org/dev/release-distribution.html#unreleased is violated. I'm afraid I still don't see how. Quoting from the policy linked above: "Unreleased materials, in original or derived form... * MUST NOT be distributed through www.apache.org/dist." Unreleased materials are not present on www.apache.org/dist. Only the absolute latest release is present (with older releases only on archive.apache.org): http://www.apache.org/dist/incubator/guacamole/ The unreleased materials for a particular RC are exposed only through the dev area of dist.apache.org: https://dist.apache.org/repos/dist/dev/incubator/guacamole/ "... * MUST NOT be distributed through channels which encourage use by anyone outside the project development community." The only distribution channel in use is the dev section of SVN dist.apache.org, the project's dev@ email list, and an unlinked page on the website reachable only through an email to that dev@ list. "... * MUST NOT be advertised to anyone outside of the project development community." The link is sent out only to the dev@ list. "... * MAY be distributed to consenting members of a development community." Which would be the dev@ list, correct? - Mike --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
