On Wed, 2017-10-11 at 07:53 -0700, Gerald B. Cox wrote: > On Wed, Oct 11, 2017 at 7:00 AM, Martin Stransky <stransky@xxxxxxxxxx> > wrote: > > > > > It's *updates*-testing repo and software in it should not be 'planned', > > > but basically 'ready' for Fedora. > > > If you want testing repo for experienced users, use COPR. > > > > > > > I don't see it that way. Is that your personal statement or is that > > written in any Fedora rules? I don't see that at Fedora page [1]. > > > > Also, the COPR suffers from some drawbacks - can't easily build from > > Fedora or other git repo [2]. > > > > ma. > > > > [1] https://fedoraproject.org/wiki/QA:Updates_Testing > > [2] I know it's supposed to work but the work flow is somehow complicated > > and uneasy and it's broken from time to time (actually right now). > > > > Martin, this is what is stated at the very top of the doc you referenced: > "The *updates-testing* repository > <https://fedoraproject.org/wiki/Repositories#updates-testing>, also > referred to as *Test Updates*, contains updates scheduled to be released > for Branched <https://fedoraproject.org/wiki/Releases/Branched> > pre-releases (after the Bodhi enabling point > <https://fedoraproject.org/wiki/Updates_Policy#Bodhi_enabling>) and stable > releases of Fedora. User testing and feedback provided via Bodhi > <http://bodhi.fedoraproject.org>, on the test > <https://admin.fedoraproject.org/mailman/listinfo/test> mailing list and > the relevant Bugzilla <http://bugzilla.redhat.com> is vital to ensure that > good updates are released quickly and bad ones kept away from release." It's worth noting that page isn't really a policy page, it's just an 'informational' page. It's not officially maintained by anyone in control of the update process, or anything. The text was probably just written by a single person, describing the process as they understand it (it may well have been me). I wouldn't rely excessively strongly on a literal reading of the text as if it were the word of law. The main official policy page regarding updates is: https://fedoraproject.org/wiki/Updates_Policy that page *is* locked to drive-by edits and *is* controlled by (IIRC) FESCo in their role as maintainers of the update process. It doesn't really have any rules, right now, about how updates-testing is to be used, but this seems like an omission. FWIW, my own belief is similar to yours and sgallagh's: updates-testing is really only intended for packages you believe there is at least a decent chance will be ready to be pushed stable. It's not really intended for sending out packages you have no intention of pushing stable. But this does seem to be a slightly unusual case, at least reading between the lines. Perhaps if Firefox 57 is a sufficiently significant update that it needs special handling, exactly how this is to be done (for all supported releases) should be discussed and arranged with FPC and/or FESCo? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
