<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 22, 2016 at 11:21 AM, Martin Sivak <span dir="ltr"><<a href="mailto:msivak@redhat.com" target="_blank">msivak@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> - you as packager / maintainer should add your build to the release<br>
> configuration file[1] or send an email with the link to your builds to the<br>
> person handling the release<br>
<br>
</span>Is there a way to automate this? Like giving you the URL of the<br>
release repository in COPR and using whatever latest package you find<br>
there?<br>
<br></blockquote><div><br></div><div>What I think we should do is to add support that once an official tag is done an official build will be triggered and done.</div><div>The question is can the official build flow be automated? IIRC it involves using tarball + signing or some other manual work which isn't</div><div>similar to the way nigthly rpms are built.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Martin<br>
<div><div class="h5"><br>
On Wed, Jun 22, 2016 at 9:44 AM, Sandro Bonazzola <<a href="mailto:sbonazzo@redhat.com">sbonazzo@redhat.com</a>> wrote:<br>
> Hi,<br>
> since it seems not clear how to get your package included in a oVirt<br>
> release, here's the procedure:<br>
> - a new build planned is communicated to <a href="mailto:devel@ovirt.org">devel@ovirt.org</a> from release<br>
> engineering team<br>
> - you as package maintainer should prepare your package to be released with<br>
> desired version (<a href="http://configure.ac" rel="noreferrer" target="_blank">configure.ac</a>, spec, whatever)<br>
> - you as packager should build your package in jenkins / koji / copr /<br>
> whatever you use to build<br>
> - you as packager / maintainer should add your build to the release<br>
> configuration file[1] or send an email with the link to your builds to the<br>
> person handling the release<br>
> - if you correctly add your package to conf files, you'll have your package<br>
> released and release notes updated.<br>
><br>
> [1] like in <a href="https://gerrit.ovirt.org/#/q/project:releng-tools+topic:releases" rel="noreferrer" target="_blank">https://gerrit.ovirt.org/#/q/project:releng-tools+topic:releases</a><br>
><br>
> Thanks<br>
> --<br>
> Sandro Bonazzola<br>
> Better technology. Faster innovation. Powered by community collaboration.<br>
> See how it works at <a href="http://redhat.com" rel="noreferrer" target="_blank">redhat.com</a><br>
><br>
</div></div>> _______________________________________________<br>
> Devel mailing list<br>
> <a href="mailto:Devel@ovirt.org">Devel@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/devel</a><br>
_______________________________________________<br>
Devel mailing list<br>
<a href="mailto:Devel@ovirt.org">Devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/devel</a><br>
<br>
<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Eyal Edri<br>Associate Manager</div><div>RHEV DevOps<br>EMEA ENG Virtualization R&D<br>Red Hat Israel<br><br>phone: +972-9-7692018<br>irc: eedri (on #tlv #rhev-dev #rhev-integ)</div></div></div></div></div>
</div></div>