Hi Radu, Whilst I agree that having to get a PMC member to move the artifacts to dist is a pain, there is a sometimes painful process we follow in Apache projects. Before a release can be made a at least 3 PMC members need to +1 the release vote, hence one of those PMC members should be available to check the vote and do the move to dist. It's one of the duties of a PMC member to ensure that the release process is executed properly.
Sling does a lot of releases. In general the process recommended by the Apache Foundation, adopted as Sling exited the incubator has served us well. Changing it seems unnecessary. However, when a member of the community contributes to such an extent that the vote and release process becomes a pain, there is a strong argument that that member should be invited to take on some PMC member responsibilities. I am sure you will hear more in due course. Best Regards Ian On 5 March 2016 at 11:06, Radu Cotescu <[email protected]> wrote: > Hi, > > Since committers can initiate releases should they also be allowed to move > the artifacts to dist, under PMC's supervision? Or should we create a > different group including just a subset of the committers (releng)? > > I'm asking this because every time I release something I have to ask the > PMC to move the artifacts to dist. While this works most of the time it > looks like the artifacts from a previous release have not made it to the > dist folder [0]. > > Thanks, > Radu > > [0] - http://sling.markmail.org/thread/37pcwcqyyb5ehann >
