Den tis 17 sep. 2019 kl 12:52 skrev Yoann Moulin <[email protected]>:
> Hello, > > >>> Never install packages until there is an announcement. > >>> > > My reaction was not on this specific release but with this sentence : « > Never install packages until there is an announcement. » And also with > this one : « If you need to do installs all the time, and can not postpone > until the repo settle. Consider rsyncing the repo after a release, > and use that for installs. » This sound crazy to me. > I would have to agree with this. If these statements are true: 1) devs say: don't install unless there is an announcement out 2) devs have previously dropped new releases before posting the announcement and told people it was a mistake to "yum upgrade"/"apt upgrade" before announcement then the solution seems very simple, do NOT populate the repos with packages that your users shouldn't install until release notes are out. I am well aware of that 100s of things around packaging and testing a release is hard, times the amount of platforms and arches you support, but to the untrained eye, not pushing packages out seems like quite a binary thing. Either you press whatever button there is that pushes the files out, or you don't press it. If there is a reason for people to not run packages until a certain condition is true, then don't press that hypothetical button until you get convinced that the condition is. Among all other things that are hard about releases, that can't be the worst? -- May the most significant bit of your life be positive.
_______________________________________________ ceph-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
