Hello, For some reason, it has not been distributed.... I will resend. In the Message; Subject : Re: MozillaFirefox 125 Message-ID : <d50cd21a-d4da-4ac0-81b6-d2a0e0f2619b@rosenauer.org> Date & Time: Mon, 29 Apr 2024 08:48:57 +0200 [WR] == Wolfgang Rosenauer <wolfgang@rosenauer.org> has written: [...] MN> > I ask you, on this occasion, why are you releasing a test version? MN> > MN> > You are right, there are many users other than Firefox who encounter MN> > problems using test versions (especially those related to MN> > KDE). However, I have never seen a comment telling people not to use MN> > test versions. MN> > MN> > Rather than not using them, it would be better not to release them. WR> to be a bit more specific: WR> In the "mozilla" repository are no test versions! WR> For test versions there would be the :beta, and :experimental WR> subprojects which are not really used currently. I thought there was a test version under the following repository: https://download.opensuse.org/repositories/home:. In fact, I've noted the following as being ambitious, but I don't make recordings, so I'm keeping it as a reference: https://build.opensuse.org/package/show/home%3AX0F%3Abranches%3Amultimedia/p.... WR> mozilla contains in 99,99% of the cases fully released upstream WR> software which is a few days later submitted - as is - to Tumbleweed. WR> Can there be issues still? - YES WR> Either caused by Mozilla releasing something broken. Just look at 125.0 and WR> 125.0.1 or because an existing patch is not fully compatible anymore. In that WR> case there is even a VERY good chance that it ends up in WR> Tumbleweed exactly the same way because it's not discovered WR> immediately and the time from upstream to TW release should be as WR> short as possible. WR> Please note that there was one incident just a few weeks ago WR> where a submission to the NSS component was killing addon signatures. WR> And because the submission looked sane and came from @suse it was WR> already in the Tumbleweed queue. So I think it was more or less WR> pure luck that it didn't get through. But on the other hand that WR> is why it has value if some people use the repo because otherwise WR> almost every issue would directly hit through to TW. I consider your e-mails showing the activities of the mainteners who support us users to be very significant. Many thanks, indeed. Anyway, if Gertjan's point is that we should not use anything other than the main repository, I basically agree. I mean, I think the Maintainers are providing the package with a focus on systemic integrity wiith targeting the main repository, so we, the users, should bear that in mind, rather than worrying about bugs. I have felt this strongly since moving to Tumbleweed. Moreover, I use YaST2 instead of the zypper command because YaST2 gives me a clear view with respect to the direction of systemic integrity. Many thanks, again & Good Night. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Microsoft is overhauling its cybersecurity strategy, called the Secure Future Initiative, to incorporate key security features into its core set of technology platforms and cloud services. " -- Microsoft overhauls cyber strategy to finally embrace security by default --