On Friday 08 June 2018 17:13:54 Konrad Windszus wrote: > +1 on letting committers copy to dist as well. We have release votes so any > PMC member can express concerns previously! Also since most of the > artifacts are anyhow consumed via Maven Central it would not be a very wise > decision to not publish a released artifact to dist (for whatever reason!)
+1 O. > > On 8. Jun 2018, at 16:48, dav...@apache.org wrote: > > > > Hi all, > > > > On 8 June 2018 at 15:29, <dav...@apache.org> wrote: > >> I will copy this release to the Sling dist directory and promote the > >> artifacts to the central Maven repository. > > > > Actually, copying to the Sling dist directory can apparently only be done > > by PMC members (see > > http://sling.apache.org/documentation/development/release-management.html# > > promoting-the-release ). > > It's a bit strange because as a committer I can publish the artifact into > > Maven Central. > > > > According to http://www.apache.org/legal/release-policy.html#upload-ci > > "The PMC can also vote to let non-PMC-members update the dist/release > > area. > > To get this set up, please open a JIRA ticket at the INFRA JIRA > > referencing > > the PMC vote." > > > > Would it be an idea to change the rules around the Sling dist directory so > > that committers can also commit to it in addition to PMC members? Then I > > can finish the tasks relating to this release without having to bother > > anyone else :) > > > > Best regards, > > > > David
