I am only curious here, ( this is mostly about mirrors and
the Rawhide repo ):
After coding changes in each package get approved, by
someone in Fedora,
I assume somebody above them in the chain-of-command,
has the authority to upload that
package to the main Fedora mirror. Right ?
If so what happens next. Does that main mirror shake hands
( fist bump ? ),
with the lesser mirrors around the world ?
I assume that from the moment the coder sends his new
changes of a specific package to his Fedora contact, that it takes
a week to reach the Rawhide repo.
I see from my perspective that when the Fedora Rawhide
Compose is posted on the listserve that it is usually two or
three days, before I get that update for any package on the list ( if I have
it installed ).
Is some of the automated parts to any process above "continuous" or
does it require someone to hit the re-build button, every day or two ?
Here is a great example:
Package: soundtracker-1.0.0.1-1.fc33
Old package: soundtracker-0.6.8-31.fc31
Old package: soundtracker-0.6.8-31.fc31
From the moment, the developer of soundtracker ( or package manager, etc ) emailed that new
updated package to someone at Fedora. How did the ball get rolling ?
Did I leave out anything worth noting ?
I guess my next question would be: do the other major distros have a similar or identical way
of doing all this upstream fancy stuff. OpenSUSE or Manjaro, for example ?
Thank you.
David Locklear
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
