sbp commented on issue #10:
URL: 
https://github.com/apache/tooling-trusted-release/issues/10#issuecomment-2734314927

   Commit bc2d3f2 adds [a 
script](https://github.com/apache/tooling-trusted-release/blob/main/scripts/release_path_parse.py)
 which performs some analysis of the paths in `dist/release`. Here is an except 
from the output:
   
   ```
   --- age ---
   
     VERSIONS: 1.1.0, 1.5.0
     SUBS: PG11, PG12, PG13, PG14, PG15, PG16, age-viewer
   
      21 ASF-CORE-VERSION-VARIANT.EXT
       3 ASF-SUB-TAG-rc2-incubating-VARIANT.EXT
   
   
   --- airavata ---
   
     VERSIONS: 0.17, 1.1
     SUBS: custos
   
       8 ASF-CORE-SUB-VERSION-VARIANT.EXT
       6 ASF-CORE-server-VERSION-VARIANT.EXT
       3 CORE-VERSION-VARIANT.EXT
       5 SUB-VERSION-VARIANT.EXT
   ```
   
   Common heuristically detected patterns in filenames have been replaced with 
uppercase variables. This gives us a quick overview of which patterns are most 
commonly used in projects for naming files, and also where these patterns are 
used inconsistently. In the example above we find that a release candidate 
version number or tag is used in a released filename, along with `-incubating`.
   
   The variables used are as follows:
   
   * ASF: `apache-` as a string constant
   * SUB: subproject name
   * VERSION: version number from a parent directory name
   * CORE: project name
   * VARIANT: whether the release is binary, source, etc.
   * TAG: version number not present in a parent directory name
   * ARCH: operating system, CPU architecture, etc.
   * EXT: extension of known artifact archives and metadata files
   
   There is also a `LABEL` variable which optionally soaks up any remaining 
unknown filename components matching a simple infix expression. Here is a list 
of all detected filename naming patterns with uses in ten projects or more. In 
other words, this isn't the total number of filenames that were named using 
this pattern, it's the number of projects that contain at least one file named 
in this way.
   
   ```
     65 ASF-CORE-VERSION-VARIANT.EXT
     32 CORE-VERSION-VARIANT.EXT
     22 SUB-VERSION-VARIANT.EXT
     21 ASF-CORE-VERSION.EXT
     20 CORE-VERSION.EXT
     19 CORE-LABEL-VERSION-VARIANT.EXT
     16 CORE-LABEL-TAG-VARIANT.EXT
     14 SUB-TAG-VARIANT.EXT
     14 CORE-TAG.EXT
     13 ASF-CORE-TAG.EXT
     13 ASF-CORE-LABEL-VERSION-VARIANT.EXT
     12 ASF-CORE-TAG-VARIANT.EXT
     12 ASF-CORE-SUB-VERSION-VARIANT.EXT
     11 ASF-SUB-VERSION-VARIANT.EXT
     11 ASF-CORE-LABEL-TAG-VARIANT.EXT
     10 CORE-SUB-TAG-VARIANT.EXT
     10 CORE-LABEL-TAG.EXT
   ```
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@tooling.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tooling.apache.org
For additional commands, e-mail: dev-h...@tooling.apache.org

Reply via email to