+1 (binding) I checked: - incubating in name - signatures and hashes exist - DISCLAIMER exists
Best regards Alin J On Wed, May 6, 2026 at 4:38 AM Justin Mclean <[email protected]> wrote: > Hi, > > +1 (binding) > > I checked: > - incubating in name > - signatures and hashes exist > - DISCLAIMER exists > - no unexpected binary files > - all files have ASF headers > - I did no compile from source > > Your releases on GitHub need some cleanup; pre-incubator releases need to > be clearly marked. I also notice that burr-0.40.1 and burr-0.40.2 were > released after you entered incubation (by 4 days). This should have gone > through the normal vote process, but they did not. The 0.41.0 release did > have a vote. > > PyPI apache-burr seems to be a placeholder as it describes itself as "A > placeholder package for a future project”. This probably should be fixed. > > The other major issue is that burr.apache.org <http://burr.apache.org/> > doesn’t have a download page. [1] ASF policy requires all projects to > maintain a release download page regardless of their primary distribution > channel. Even though Burr distributes primarily via PyPI, the download page > serves as the authoritative public record of official ASF releases, directs > users to verify signatures and checksums, and makes clear which releases > have been approved by the IPMC. > > Kind Regards, > Justin > > 1. https://www.apache.org/legal/release-policy.html#publication > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
