> When MySQL 8 is being developed and being packages as module, do you > build the module for Rawhide only or for all Fedoras? > > If you build it for all Fedoras, how do you deal with incompatible > changes during the MySQL 8 developement. I'm hitting on the Fedora > Updates Policy that forbids incompatible changes in stable Fedoras. > > If you build it for Rawhide only, how do you ensure that the module is > not inheritted into a stable Fedora on branching. Because in case of > branching F31 relengs tried very hard to branch the module and rebuild > them. (Despite I told them not to do that with perl:5.26.) That's a great observation. Ususally when the package (module in this case) is prone to breaking bugs, I develop it in Rawhide and only later, (e.g. Beta, but it depends from upstream to upstream) I extend the build to other Fedoras. > I'm still missing an offical recognition that there can be modules under > development in stable Fedora. Otherwise we have no way of developing new > modules. Fedora tries very hard to align module lifecycle to Fedora > lifecycle. It does not work for me. That's surely an *absolute need* to have an option to mark a module as "under developement" or something simmilar and have that anchored in the guidelines, if we want to use this chance a modularity technically offers. -- Michal Schorm Software Engineer Core Services - Databases Team Red Hat -- On Thu, Sep 19, 2019 at 2:33 PM Petr Pisar <ppisar@xxxxxxxxxx> wrote: > > On 2019-09-19, Michal Schorm <mschorm@xxxxxxxxxx> wrote: > > While the new major version of the database is being developed, I'd > > love to pack it in Fedora, test it, offer it to the users and provide > > feedback to the upstream, solving the uprising issues with them way > > before the GA. > > Because I want to keep a stable version in the base Fedora, I'm using > > modules to provide both of them. > > E.g. when MySQL 8 was being developed ( pre-GA releases ), I normally > > maintained the MySQL 5.7 (latest stable major version) in the base > > Fedora, while having MySQL 8 as a module. > > > When MySQL 8 is being developed and being packages as module, do you > build the module for Rawhide only or for all Fedoras? > > If you build it for all Fedoras, how do you deal with incompatible > changes during the MySQL 8 developement. I'm hitting on the Fedora > Updates Policy that forbids incompatible changes in stable Fedoras. > > If you build it for Rawhide only, how do you ensure that the module is > not inheritted into a stable Fedora on branching. Because in case of > branching F31 relengs tried very hard to branch the module and rebuild > them. (Despite I told them not to do that with perl:5.26.) > > I'm still missing an offical recognition that there can be modules under > development in stable Fedora. Otherwise we have no way of developing new > modules. Fedora tries very hard to align module lifecycle to Fedora > lifecycle. It does not work for me. > > -- Petr > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-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/devel@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-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/devel@xxxxxxxxxxxxxxxxxxxxxxx
