Going only by past experiences in the incubator, my understanding is that a graduation blocking issue is not something that necessarily blocks a podling release. It would be something that should be noted and fixed in follow up releases for sure. Perhaps the letter of the law change or the level of enforcement has changed since then.
Now, whether those experiences were to the letter of the law or not, I believe that (especially the first) release from a podling is intended to make sure that the mechanics of creating an Apache release are understood. I do think that the mechanics are in order here and would expect that this should be able to move forward with a JIRA to fix in a follow up release. On Wed, Jun 26, 2019 at 12:44 AM Justin Mclean <jus...@classsoftware.com> wrote: > Hi, > > I also find int a little odd that in the discussion on this release it was > not clearly pointed out that having compiled code in the source release is > a graduation blocking issue and that as a TLP this would not be allowed in > a release, especially given that the exact same issue occurred in the > previous release. Now it may be at some point policy will change and allow > this, but currently it doesn’t. > > I’ve asked on users@infra if infra will allow this release, and in > general releases like this. [1] > > Thanks, > Justin > > 1. > https://lists.apache.org/thread.html/a9d158ba394de3ac23204c4b7cd7e377271eb24035a38ee137a54786@%3Cusers.infra.apache.org%3E > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
