Jeff, in the other thread you mentioned “I personally have been thinking of the models as convenience binaries”.
I think that’s the most obvious answer and is what I’d think too. If that’s the case, then the policies suggest that the version needs to match the version they’re created from. So should this be something like opennlp-ud-models-1.0-1.9.3 or similar? The other thing, which is murky in practice, is that do the models need to be voted on concurrently with a release or just created by the PMC from an official release and published on Apache supported infrastructure? Direct binary artifacts are almost always evaluated at the time of a release vote but more derivative ones often aren’t. E.g., a lot of projects publish Docker images from approved releases but not with an independent vote. Which are these? Incubator recently published some helpful guidelines which clarify related stuff for the podlings: https://incubator.apache.org/guides/distribution.html -joey > On Mar 15, 2021, at 3:26 PM, Jeff Zemerick <jzemer...@apache.org> wrote: > > Before starting a second release vote thread for the OpenNLP models and > since this is the first release of pretrained OpenNLP models, I would like > to pause to solicit feedback from the community in regards to the release > configuration. > > - The files are staged on the ASF dev SVN at > https://dist.apache.org/repos/dist/dev/opennlp/ud-models-1.0/. > - The model files are signed and hashed. > - Includes README, CHANGES, NOTICE, and LICENSE files. > - The training and evaluation outputs are in the training-eval-logs.zip > file (also signed and hashed). > > Please let me know if anything is missing or should be changed. Once things > are in a good state I will make a PR to document the steps on the website > (OPENNLP-1328) and start a vote thread. > > ASF Release Creation Process: > https://infra.apache.org/release-publishing.html > > Thanks, > Jeff
