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: [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]
