> - you as packager / maintainer should add your build to the release > configuration file[1] or send an email with the link to your builds to the > person handling the release
Is there a way to automate this? Like giving you the URL of the release repository in COPR and using whatever latest package you find there? Martin On Wed, Jun 22, 2016 at 9:44 AM, Sandro Bonazzola <[email protected]> wrote: > Hi, > since it seems not clear how to get your package included in a oVirt > release, here's the procedure: > - a new build planned is communicated to [email protected] from release > engineering team > - you as package maintainer should prepare your package to be released with > desired version (configure.ac, spec, whatever) > - you as packager should build your package in jenkins / koji / copr / > whatever you use to build > - you as packager / maintainer should add your build to the release > configuration file[1] or send an email with the link to your builds to the > person handling the release > - if you correctly add your package to conf files, you'll have your package > released and release notes updated. > > [1] like in https://gerrit.ovirt.org/#/q/project:releng-tools+topic:releases > > Thanks > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > > _______________________________________________ > Devel mailing list > [email protected] > http://lists.ovirt.org/mailman/listinfo/devel _______________________________________________ Devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/devel
