Re: Committer access to sling-dist (Was: Re: [RESULT][VOTE] Release Apache Sling Feature, Feature-IO, Feature-Analyser and Feature-ModelConverter 0.1.2)
Hi David, On Tue, Jun 12, 2018 at 3:32 PM Bertrand Delacretaz wrote: > ... wrote: > > ...I would like to request access - have another release to go in :).. FYI we haven't made a decision on this yet - if you need to copy files to the dist folder please ask for help here and one of us will jump in! -Bertrand
Re: Committer access to sling-dist (Was: Re: [RESULT][VOTE] Release Apache Sling Feature, Feature-IO, Feature-Analyser and Feature-ModelConverter 0.1.2)
On Tue, Jun 12, 2018 at 1:04 PM David Bosschaert wrote: > ...I would like to request access - have another release to go in :).. Ok. I'll start a lazy 24-hours vote on our private list, to have a traceable PMC decision on this. And in parallel ask ASF infra if that's something we can do ourselves or how to best handle the authorizations. -Bertrand
Re: Committer access to sling-dist (Was: Re: [RESULT][VOTE] Release Apache Sling Feature, Feature-IO, Feature-Analyser and Feature-ModelConverter 0.1.2)
Hi all, > > ...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?... > I'm fine with that, for specific committers who ask for access. I would like to request access - have another release to go in :) Best regards, David On 11 June 2018 at 09:55, Bertrand Delacretaz wrote: > Hi, > > On Fri, Jun 8, 2018 at 4:48 PM wrote: > > ...It's a bit strange because as a committer I can publish the artifact > into > > Maven Central... > > Maven Central is not an official source of Apache Releases, even > though our release archives do also end up there. > > > ...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?... > > I'm fine with that, for specific committers who ask for access. > > The svn notifications for > https://dist.apache.org/repos/dist/release/sling/ go to > comm...@sling.apache.org, so we have reasonable PMC oversight. > > -Bertrand >
Re: Committer access to sling-dist (Was: Re: [RESULT][VOTE] Release Apache Sling Feature, Feature-IO, Feature-Analyser and Feature-ModelConverter 0.1.2)
Hi, On Fri, Jun 8, 2018 at 4:48 PM wrote: > ...It's a bit strange because as a committer I can publish the artifact into > Maven Central... Maven Central is not an official source of Apache Releases, even though our release archives do also end up there. > ...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?... I'm fine with that, for specific committers who ask for access. The svn notifications for https://dist.apache.org/repos/dist/release/sling/ go to comm...@sling.apache.org, so we have reasonable PMC oversight. -Bertrand
Re: Committer access to sling-dist (Was: Re: [RESULT][VOTE] Release Apache Sling Feature, Feature-IO, Feature-Analyser and Feature-ModelConverter 0.1.2)
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, 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
Re: Committer access to sling-dist (Was: Re: [RESULT][VOTE] Release Apache Sling Feature, Feature-IO, Feature-Analyser and Feature-ModelConverter 0.1.2)
+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!) > On 8. Jun 2018, at 16:48, dav...@apache.org wrote: > > Hi all, > > On 8 June 2018 at 15:29, 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
Committer access to sling-dist (Was: Re: [RESULT][VOTE] Release Apache Sling Feature, Feature-IO, Feature-Analyser and Feature-ModelConverter 0.1.2)
Hi all, On 8 June 2018 at 15:29, 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
