On Monday, February 20, 2017 6:44:50 PM CET Jan Kurik wrote: > Fedora will no longer produce Alpha releases. As a side-effect of making rawhide "alpha". That doesn't sound bad. After seeing Denis's talk on devconf, I think I understand the motivation: it takes ages to generate all the Fedora related products like images. Right? > == Detailed Description == > By gating Rawhide builds from landing in the compose and gating the > publication of composes on automated test results we will ensure Rawhide will > always be at Alpha quality. This will make it more generally useful to people > as a daily driver and development platform, and mean we no longer need to go > through the process of building, testing and shipping Alpha releases. The > initial testing will be ensuring that a package is installable and that it > does not break existing packages installation. Ok, I'm curious why we'll treat CI/testing differently on stable releases and on fedora. AFAIK, _bodhi_ runs the tests for stable releases, and for Rawhide it will be koji directly? Why you don't move all the testing to koji then? >From this perspective, this sounds like we invent sub-optimal (release engineering) and confusing (for packager's) workflow. > Over time we can enable extra testing to gate the build going into > rawhide. Builds will land in the buildroot to be built against before > they make it to the compose. It is not specified, but there will be two sets of tests? One to even move the package to buildroot to build against, and second to move the package to rawhide repo, right? Then what about to do apply the same process for updates-testing? Pavel _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
