Docs:/streams: try to explain streams lifecycle #1736
Conversation
I have been struggling a bit to understand how the content is promoted between the streams, so I tried to improve the documentation a little. I thought of adding a mermaid chart as well but I am not sure if it's really helpful. Also, delete bodhi-updates references, see coreos#1734
| #### Regular State | ||
| Although all the streams are built from scratch (there is no tangible relations between streams) here is how the RPMs flow towards stable: | ||
|
|
||
| The **testing-devel** Stream is built daily with the content of the `fedora-update` repository. If the build successfully pass the tests, |
There was a problem hiding this comment.
Which fedora-update repository are you referring to here?
There was a problem hiding this comment.
| Any new RPM receive the `coreos-pool` koji tag. | ||
|
|
||
| For a release (approximately every two weeks), someone manually triggers the `bump-lockfile` job to propagate the **testing** content to the **stable** branch. | ||
| The **testing-devel** content is propagated to the **testing** and **next** streams. Theses images are built from the `coreos-pool` yum repository. |
There was a problem hiding this comment.
Is it not testing-devel -> next -> testing -> stable? Reading this I feel you're saying that testing-devel goes directly to both ( testing <- testing-devel -> next).
There was a problem hiding this comment.
when Fedora is not branched (right now), testing and next are the same .
Looking at testing commit history : it's at testing devel e13ff7d
Looking at next commit history : it's at testing devel e13ff7d
|
|
||
| #### When Fedora Branched exist | ||
|
|
||
| Before every released, there is a stabilisation period. A branch is created from rawhide, the next release enters it's [branched](https://docs.fedoraproject.org/en-US/releases/branched/) state. |
There was a problem hiding this comment.
nit-pick: Before every release, ...
|
|
||
| #### Rawhide | ||
|
|
||
| The **rawhide** stream is daily built from the `fedora rawhide packages. When there is no `fedora-branched` release, the **branched** stream mirrors |
| #### Rawhide | ||
|
|
||
| The **rawhide** stream is daily built from the `fedora rawhide packages. When there is no `fedora-branched` release, the **branched** stream mirrors | ||
| **rawhide**. This stream allow us to monitor changes early and react accordingly. The results are not used in any lockfiles. |
There was a problem hiding this comment.
That's interesting... honestly, this is the first time I'm considering the lifecycle as a whole. I feel like a chart would help clarify things described above ;)
|
There are multiple things here in both the old and new texts that aren't quite right/outdated. Some things in the new text also duplicate other sections. WDYT about instead focusing this PR on scrubbing out bodhi-updates and bodhi-updates-testing for now and I can do a follow-up that updates this doc more generally to reflect reality? |
You are right let's split that out: #1738 |
|
@jlebon BTW, what do you think about merging
If you don't mind I'd like to do the follow-up on the doc update. I know it's going to be a slower process, but IMHO the process of figuring this out is valuable :) |
The difference is that the text in I do think though that
Works for me! |
I have been struggling a bit to understand how the content is promoted between the streams, so I tried to improve the documentation a little.
I thought of adding a mermaid chart as well but I am not sure if it's really helpful.
Also, delete bodhi-updates references, see #1734