You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tooling.apache.org by "dave2wave (via GitHub)" <gi...@apache.org> on 2025/09/03 21:28:58 UTC

[I] Provide project lifecycle information as part of the release (tooling-trusted-release)

dave2wave opened a new issue, #222:
URL: https://github.com/apache/tooling-trusted-release/issues/222

   We should provide lifecycle information so that consumers have some idea of the lifecycle promises for a project and this major version.


-- 
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-unsubscribe@tooling.apache.org.apache.org

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


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


Re: [I] Provide project lifecycle information as part of the release (tooling-trusted-releases)

Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #222:
URL: https://github.com/apache/tooling-trusted-releases/issues/222#issuecomment-3534833323

   I think that we may be able to automate the construction of these pattern simply by analyzing versions and the order of releases. I think we can see most of the patterns even in the few Alphas we have had.
   
   Lifecycle events happen from within the Catalog model.
   
   I backed off the explicit model after I saw a discussion about `latest` problems in #maven slack channel.


-- 
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-unsubscribe@tooling.apache.org

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


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


Re: [I] Project lifecycle information as part of the release catalog (tooling-trusted-releases)

Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #222:
URL: https://github.com/apache/tooling-trusted-releases/issues/222#issuecomment-3745425995

   #183 is now well defined with lifecycle.


-- 
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-unsubscribe@tooling.apache.org

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


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


Re: [I] Project lifecycle information as part of the release catalog (tooling-trusted-releases)

Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #222:
URL: https://github.com/apache/tooling-trusted-releases/issues/222#issuecomment-3693425599

   The daily [cronjob](https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/scripts/cronjobs/parsereleases.py) run to support `projects.apache.org` uses previously created on `downloads.apache.org` `find_ls` file and classifies current source releases. By looking at:
   
   ```
   def cleanFilename(filename):
       """
           Attempts to determine the release id to which a file belongs
           Strips extensions such as .tgz etc, then suffixes such as -sources
           Replaces qualifiers such as -assembly- by '-'
           Returns the simplified filename .
   
           N.B. the ordering is significant, as the list is only scanned once
       """
       for suffix in ['-all', '-src', '_src', '.src', '-sources', '_sources', '-source', '-bin', '-dist',
                      '-source-release', '-source-relase', '-tests', '-test', '-debug', '-uber',
                      '-macosx', '-distribution', '-example', '-native', '-win', '-win32', '-linux', '-pack', '-packaged', '-current', '-embedded',
                      '-py', '-py2', '-py2.6', '-py2.7', '-no', 'unix-distro', 'windows-distro', 'with', '-dep', '-standalone', '-webapp', '-dom', '-om',
                      '-32bit', '-i386', '_i386', '.i386', '-minimal', '-jettyconfig', '-py2.py3-none-any', 'newkey', 'oldkey', 'jars', '-jre13', '-hadoop1', '-hadoop2', '-project',
                      '-with-dependencies', '-client', '-server', 'server-webapps', '-full', '-all', '-standard', '-for-javaee', '-for-tomcat',
                      'hadoop1-scala2', '-deployer', '-fulldocs', '-embed', '-apps', '-app', '-ref', '-installer', '-bundle', '-java']:
           # The above list could be simplified further
           if filename.endswith(suffix):
               filename = filename[0:len(filename)-len(suffix)]
       # COMDEV-535: No longer strip '-parent-', as that may be needed
       for repl in ['-assembly-', '-minimal-', '-doc-', '-src-', '-webapp-', '-standalone-', '-project-', '-win32-']:
           filename = filename.replace(repl, '-')
       return filename
   ```
   
   You will find suffixes to consider "sources" rules. [`releases.json`](https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/site/json/foundation/releases.json) and [`releases-files.json`](https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk/site/json/foundation/releases-files.json)
   
   The weakness in this p.a.o code is that it does not do well in identifying sub-projects. Look at airflow_providers, beam, etc, but this is close.
   
   


-- 
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-unsubscribe@tooling.apache.org

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


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


Re: [I] Project lifecycle information as part of the release catalog (tooling-trusted-releases)

Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave closed issue #222: Project lifecycle information as part of the release catalog
URL: https://github.com/apache/tooling-trusted-releases/issues/222


-- 
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-unsubscribe@tooling.apache.org

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


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


Re: [I] Provide project lifecycle information as part of the release (tooling-trusted-releases)

Posted by "sbp (via GitHub)" <gi...@apache.org>.
sbp commented on issue #222:
URL: https://github.com/apache/tooling-trusted-releases/issues/222#issuecomment-3458446311

   We decided today that we will allow users to specify release version patterns which will be associated with lifecycle statuses such as LTS. We did not yet decide on a complete enumeration of lifecycle statuses and plan to research this.


-- 
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-unsubscribe@tooling.apache.org

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


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


Re: [I] Provide project lifecycle information as part of the release (tooling-trusted-releases)

Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #222:
URL: https://github.com/apache/tooling-trusted-releases/issues/222#issuecomment-3457866354

   Projects have different LifeCycle strategies which follow the following patterns:
   
   1. Linear **timeline**. Releases proceed from one version to the next without branching. Versions in this approach might look like `0.1.0`, `0.1.1`, `0.1.2`, `0.2.0`, `0.3.0`, ...
   2. Version **table**. Releases may proceed on different version **timelines** in parallel. This would look like _version 1_: `1.0.0`, `1.0.1`, `1.1.0`; _version 2_: `2.0.0`, `2.0.1`. With a version table particular version lines ay be marked as **LTS** which means they will be supported for longer than later version lines that are not **LTS**.
   
   Each version timeline has a series of common **LifeCycle Events** which indicate which versions are live, archived, still supported, and are the "latest".


-- 
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-unsubscribe@tooling.apache.org

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


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


Re: [I] Project lifecycle information as part of the release catalog (tooling-trusted-releases)

Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #222:
URL: https://github.com/apache/tooling-trusted-releases/issues/222#issuecomment-3684235251

   See #183 - let's construct clear design schema by discussing these two issues together


-- 
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-unsubscribe@tooling.apache.org

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


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