... | @@ -118,7 +118,7 @@ Version: `<year>(.<parents_stream_ids>)+.<id>` |
... | @@ -118,7 +118,7 @@ Version: `<year>(.<parents_stream_ids>)+.<id>` |
|
|
|
|
|
Each ELT Platform's Yearly and Release Streams has defined its End Of Life date. Platform EOL has two phases. In the EOL Phase 1, given ELT Platform Stream is usable, but it shouldn't be used for development. In that phase, CI and OBS re-builds are not available. All ELT subsystems and instruments must plan to update to a newer platform version before EOL Phase 2.
|
|
Each ELT Platform's Yearly and Release Streams has defined its End Of Life date. Platform EOL has two phases. In the EOL Phase 1, given ELT Platform Stream is usable, but it shouldn't be used for development. In that phase, CI and OBS re-builds are not available. All ELT subsystems and instruments must plan to update to a newer platform version before EOL Phase 2.
|
|
|
|
|
|
** EOL Phase 1 **
|
|
**EOL Phase 1**
|
|
|
|
|
|
The EOL Phase 1 for a Yearly or Release Stream starts 6 months after the new Yearly or Release Stream is available.
|
|
The EOL Phase 1 for a Yearly or Release Stream starts 6 months after the new Yearly or Release Stream is available.
|
|
|
|
|
... | @@ -130,7 +130,7 @@ The EOL Phase 1 for a Yearly or Release Stream starts 6 months after the new Yea |
... | @@ -130,7 +130,7 @@ The EOL Phase 1 for a Yearly or Release Stream starts 6 months after the new Yea |
|
* Packages and installation scripts are available.
|
|
* Packages and installation scripts are available.
|
|
* The ELT DevEnv team may postpone this phase for a cost of 0.1 FTE yearly, covered by the requesting party.
|
|
* The ELT DevEnv team may postpone this phase for a cost of 0.1 FTE yearly, covered by the requesting party.
|
|
|
|
|
|
** EOL Phase 2 **
|
|
**EOL Phase 2**
|
|
|
|
|
|
The EOL Phase 2 for a Yearly or Release Stream starts 5 years after EOL Phase 1.
|
|
The EOL Phase 2 for a Yearly or Release Stream starts 5 years after EOL Phase 1.
|
|
|
|
|
... | | ... | |