> (Incidentally, I find it somewhat questionable that releases are treated differently than the ongoing publication of merged work. Why are released binaries treated differently than source code?)
I believe this stems from the fact that at least according to Apache, the only thing they consider a release is the source code (which gets pushed to an SVN repository as part of the process). Anything aside from that (i.e. deploying jar's to sonatype/maven) is secondary and technically not part of the Apache release. Then again it appears that its not releases where the headers are critical but rather incubation to a TLP which muddies it even further. On Thu, Nov 17, 2022 at 4:50 PM Johannes Rudolph <[email protected]> wrote: > On Thu, Nov 17, 2022 at 4:09 PM Claude Warren, Jr > <[email protected]> wrote: > > For the moment the Incubator PMC is the arbiter as all releases are under > > the auspices of the incubator. > > > > When Pekko graduates, the Pekko PMC will be the arbiter. And the Pekko > PMC > > Chair will be responsible to Legal for IP issues. > > Based on the scale of the project, this will set up the PMCs to be in > a bad position, because they have either to trust a big list of > committers to have carefully vetted each single change, or, they have > to do their own due diligence and go through 10ks of changes. Who > would want to greenlight a release under those conditions? > > (Incidentally, I find it somewhat questionable that releases are > treated differently than the ongoing publication of merged work. Why > are released binaries treated differently than source code?) > > Johannes > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Matthew de Detrich *Aiven Deutschland GmbH* Immanuelkirchstraße 26, 10405 Berlin Amtsgericht Charlottenburg, HRB 209739 B Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen *m:* +491603708037 *w:* aiven.io *e:* [email protected]
