I only occasionally see incubating in jar versions. I prefer the idea of requiring having the DISCLAIMER in the META-INF within the jar alongside the LICENSE and NOTICE files.
On Fri 21 Nov 2025, 13:02 Stamatis Zampetakis, <[email protected]> wrote: > +1 on what Justin said. I was in the process of sending a similar > response. The four items are more like best/common practices rather > than actual policy violations. > > Best, > Stamatis > > On Fri, Nov 21, 2025 at 12:58 PM Justin Mclean <[email protected]> > wrote: > > > > Hi, > > > > Thanks for looking into this release in detail; I haven't, but off the > top of my head. > > > > > 1. Missing RC designation in release URL > > > > This is not a requirement, and projects can name releases when they > want. While using RC X is common, it’s not required. That naming does make > it easy if another candidate for the release is needed. > > > > > 2. Multiple repositories bundled in single vote (requires separate > votes) > > > > This is fine, and many projects do this. > > > > > 3. Built artifacts missing "incubating" suffix (98.3% non-compliant) > > > > Official releases on Infra-supported platforms need to be named this > way, so yes, I think there seems to be an issue here, but perhaps this has > not been common practice and has been missed. What may be more important is > do the jars include an incubator disclaimer? > > > > > 4. Premature release tagging before vote completion > > > > GitHub tags are irrelevant as they are mutable; it's the hash that > matters. > > > > Kind Regards, > > Justin > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
