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

   ## Cycle schema
   
   Automatically have one per project
   
   field | description
   ---------|---------
   cycle_key | project_key and cycle combined
   cycle | a version matched cycle
   project_key | project this cycle belongs to.
   start | the date of the first release
   begin | the date of the first release candidate
   latest | the date of the latest release
   eod | True/false or date eol - no more development 
   eos | True/false or date cycle will be eos - only security patches
   eol | True/false or date cycle will be eol - no more support
   lts | True/false is this an LTS cycle
   
   ## Project version and cycle metadata
   
   field | description
   --------|--------
   method | Semver, calver, simple. adjusts the pattern 
   pattern | Regex for validating a version string
   cycle match | Regex to detect the cycle from the version string. Blank if 
not using cycles.
   branch | template to create a cycle's git repository branch. Blank means the 
default branch.
   
   ## Lifecycle event schema
   
   Event | Type | Description
   -------|-------|-------------
   release | version | A release is finished event.
   eod | project cycle | End of development on a release cycle
   eos | project cycle | End of support on a release cycle
   eol | project cycle | End of life on a release cycle
   archive | version | One or more releases are archived.
   withdraw | version | A new release has a problem - it has been removed (as 
much as possible)
   
   Fields include:
   
   1. project_key
   2. cycle_key
   3. version_key
   4. event
   5. datetime
   6. reference urls
   
   We will want to search matching on these three project, cycle, and version 
in one of these three combinations:
   
   1. project
   2. project, cycle
   3. project, cycle, 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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to