<div dir="ltr">Hi,<div>since it seems not clear how to get your package included in a oVirt release, here's the procedure:</div><div>- a new build planned is communicated to <a href="mailto:devel@ovirt.org">devel@ovirt.org</a> from release engineering team</div><div>- you as package maintainer should prepare your package to be released with desired version (<a href="http://configure.ac">configure.ac</a>, spec, whatever)</div><div>- you as packager should build your package in jenkins / koji / copr / whatever you use to build</div><div>- 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</div><div>- if you correctly add your package to conf files, you'll have your package released and release notes updated.<br clear="all"><div><br></div><div>[1] like in <a href="https://gerrit.ovirt.org/#/q/project:releng-tools+topic:releases">https://gerrit.ovirt.org/#/q/project:releng-tools+topic:releases</a></div><div><br></div><div>Thanks</div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr">Sandro Bonazzola<br>Better technology. Faster innovation. Powered by community collaboration.<br>See how it works at <a href="http://redhat.com" target="_blank">redhat.com</a><br></div></div></div></div>
</div></div>