> I assume you’re aware that the workflow change only excludes the tag v0.7.1, so any other tag still publishes to crates.io.
Yes. I will go through the ASF release process for 0.7.2. Working on license provances issues and would prepare a release candidate. > So deleting DISCLAIMER leaves the podling with no incubation disclaimer at all, and we need one in all documentation and releases. A different disclaimer message also needs IPMC approval first. > I don't think WIP is what you want anyway. It's for ASF releases that don't follow all ASF policy, and it needs a list of known issues. Good to know. I'll revert the DISCLAIMER-WIP to the original DISCLAIMER as we are going to make an ASF release. Best, tison. Justin Mclean <[email protected]> 于2026年9月4日周五 13:43写道： > HI, > > Thanks for yanking it. > > On #278, the DISCLAIMER-WIP file doesn't contain the WIP disclaimer. That > text is the incubation statement that some releases may not be fully > compliant with ASF policy, a list of the issues you're aware of, and the > note that downstream users need their own licensing review. What's there is > a note that 0.7.1 is not an ASF release, which is a different thing. > > So deleting DISCLAIMER leaves the podling with no incubation disclaimer at > all, and we need one in all documentation and releases. A different > disclaimer message also needs IPMC approval first. > > I don't think WIP is what you want anyway. It's for ASF releases that > don't follow all ASF policy, and it needs a list of known issues. > > I assume you’re aware that the workflow change only excludes the tag > v0.7.1, so any other tag still publishes to crates.io. > > Kind regards, > > Justin
