> On Mar 31, 2026, at 10:45 AM, Henrik Ingo <[email protected]> wrote:
> 
> On Tue, Mar 31, 2026 at 8:00 AM Austin Bennett <[email protected]>
> wrote:
> 
>> Well, I didn't even think about permissions.
>> 
>> Since I am not a committer here, I can't merge stuff, doesn't look like can
>> run ci, etc.  So, can't even do much with dependabot, etc.
>> 
>> 
> Oh, sorry about that. Since you had an apache.org address I assumed you
> volunteered because you would have some other permissions that I didn't
> know about, perhaps via the Incubator PMC or something.
> 
> So I can do the release, no problem. It's supposed to rotate around the
> PPMC members anyway. This is a requirement in the incubation process.
> 
> 
>> Since I haven't done much for the community, I can understand why I don't
>> have that ability [ ex: committer ].  But, that puts me in a not great
>> place to actually get things done, as otherwise seems like alot of friction
>> :-/ to ask people to perform basic actions around things like version
>> bumps, pinning dependencies, basic repo hygeine .  Not sure how to
>> resolve(?), so I guess I can find other opportunities for contributing more
>> easily.
>> 
>> Yes, def requires PMC for keys/signing.
>> 
>> 
> For sure. The release process is quite bureaucratic compared to everything
> else. For a good reason, of course.

For your next release please give the new Apache Trusted Releases process a try.

https://release-test.apache.org/#project-otava

I’m managing this development and have tested with the last Otava release. We 
are getting close to a Beta release.

Best,
Dave

> 
> I would say there's no reason to let this be demotivating. After a year+ of
> upgrading python versions, writing out dependencies, etc... We are finally
> in a position where it is possible for new (and not so new) contirbutors to
> work on meaningful tasks.
> 
> henrik
> 
> 
> -- 
> *nyrkio.com <http://nyrkio.com/>* ~ *Continuous Benchmarking as a Service*
> 
> Henrik Ingo, CEO
> [email protected]                               LinkedIn:
> www.linkedin.com/in/heingo
> +358 40 569 7354                                 Twitter: twitter.com/h_ingo

Reply via email to