Hi

As you may have seen on DEV then we have trouble releasing 4.14.3 as we
cannot promote the binaries to maven staging repo due to some weird nexus
error.

That error indicate its due to MD5 checksum file that has a magic starting
byte combination that nexus mistakenly identify as a binary file; or at
least that is what AI bot and some reports on the internet had said in the
past.

Anyway MD5 is oudated. And so is SHA1. Maybe we should look into dropping
these and jump to a newer such as SHA256

Also we can get in touch with other ASF projects, and there must be some of
those that have done that.



-- 
Claus Ibsen

Reply via email to