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. - Mike --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
