Matthew is correct, the release is the source code. Everything else is considered a user convenience.
And yes, for large scale projects being a PCM member is a lot of work. And yes there is a level of trust between the PCM and the committers. And part of the Incubation process is to ensure that that trust exists, and to get processes embedded in the culture of the project. For a release the questions are: 1. Does the code have the right licensing 2. Are there additional licenses that are required to be included? 3. Can the product be built from the source? 4. Are the jars and additional convenience items properly signed? 5. Do the jars and additional convenience items contain the result of source compilation? If so and if the project has determined that the code is of sufficient quality then it can be released. And yes, as we work through Pekko we will find things that are edge and corner cases for the standard Apache release process. We, as a team, will determine how that should work and the Incubator will help us make sure that what we decide meets the requirements of Apache. Once ouf of the incubator, all of the process will be second nature. We are currently in the hard part -- understanding the Apache requirements and how to apply them to what was the Akka development model to achieve an Apache Pekko development model. On Thu, Nov 17, 2022 at 3: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] > >
