On Thu, Sep 19, 2019 at 8:33 AM Petr Pisar <ppisar@xxxxxxxxxx> wrote: > > 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. > I just opened https://pagure.io/modularity/issue/156 to make a proper policy decision on this, including my recommendation: *** * It is not permissible to make a prerelease stream the default stream for a module in any release.(*) * It is permissible to include a pre-release stream in Rawhide at any time. * It is permissible to include a pre-release stream in a stable branch of Fedora if the stream name clearly identifies it as unstable in some manner. When the stream is ready to be treated as stable, a new stream should be created with an [appropriate name](https://docs.fedoraproject.org/en-US/modularity/making-modules/naming-guidelines/#_module_stream_name) (such as a version number or other indicator of API/UX compatibility). (*) Note that this is different from a "rolling" stream, in that the expectation on rolling streams are that all of the updates are stable, not that they are experimental and might change. *** _______________________________________________ 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
