+1 (binding)
Den tors. 2. jul. 2026 kl. 17.31 skrev Walter Duque de Estrada < [email protected]>: > +1 binding > > > Walter > > > On Jul 2, 2026, at 8:57 AM, Tyler VanZanten <[email protected]> > wrote: > > > > +1 (biding) > > > > On Thu, Jul 2, 2026 at 9:36 AM James Fredley <[email protected]> > > wrote: > > > >> Hello everyone, > >> > >> As part of ongoing improvements to our release process on GitHub, I > >> would like to propose creating a dedicated GitHub team to handle > >> approval steps in the release workflow. > >> > >> Current situation > >> Our release workflow includes steps that require approval. Today we > >> manage this by manually adding individual GitHub user accounts to the > >> approval configuration (in the workflow or repository settings) whenever > >> the list of approvers changes. This approach is repetitive and > error-prone. > >> > >> Proposal > >> Create a GitHub team called Grails Release Managers (suggested slug: > >> `grails-release-managers` or similar) under the Apache Grails GitHub > >> organization. > >> > >> Once the team exists, we can update the release workflow configuration > >> to require approval from members of this team instead of listing > >> individual users. After that change, adding or removing release managers > >> becomes a simple team membership update. No further edits to the > >> workflow file or settings are needed for personnel changes. > >> > >> This pattern is used by other Apache projects and makes release > >> management cleaner and more scalable. It also gives the PMC a clear, > >> centralized place to manage who holds release approval rights. > >> > >> If the PMC approves, I will submit a request to ASF Infrastructure to > >> create the team. Once it is available, we will update the workflow > >> configuration and begin using the team for release approvals. > >> > >> Vote > >> Please vote on the following resolution: > >> > >> [VOTE] Approve creation of a GitHub team ("Grails Release Managers") so > >> the release workflow can use team-based approvals instead of manually > >> maintained lists of individual users. This will allow the PMC to manage > >> release approvers more easily by adding or removing people from the > team. > >> > >> - +1 — Approve > >> - 0 — Abstain > >> - -1 — Do not approve (please explain your concern) > >> > >> > >> The vote will stay open for at least 72 hours (or longer if discussion > >> continues). If there is lazy consensus or clear approval, we will > >> proceed with the Infrastructure request. > >> > >> Thank you for your input on this operational improvement. > >> > >> My vote: > >> > >> +1 (binding) > >> > >> Best regards, > >> James Fredley > >> VP and Chair, Apache Grails PMC > >> Apache Software Foundation > >> > > -- Best regards Søren Berg Glasius Apache Groovy™ and Apache Grails® PMC --- Press ESC once to quit - twice to save the changes.
