<div dir="ltr">Looks like the congress job is working now. We have a tarball for our latest RC:<div><br></div><div><a href="http://tarballs.openstack.org/congress/congress-3.0.0.0rc3.tar.gz">http://tarballs.openstack.org/congress/congress-3.0.0.0rc3.tar.gz</a><br></div><div><br></div><div>Thierry added the links back for the tarball.</div><div><br></div><div><a href="https://github.com/openstack/releases/commit/beee35379b3b52ed7d444d93d7afd8b6603f69b6">https://github.com/openstack/releases/commit/beee35379b3b52ed7d444d93d7afd8b6603f69b6</a><br></div><div><br></div><div>So it looks like everything is back on track for the Congress Mitaka release. Let me know if there's anything else I need to do.</div><div><br></div><div>Thanks for all the help release team!</div><div>Tim</div><div><br><br><div class="gmail_quote"><div dir="ltr">On Sat, Apr 2, 2016 at 5:39 AM Doug Hellmann <<a href="mailto:doug@doughellmann.com">doug@doughellmann.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Excerpts from Tim Hinrichs's message of 2016-04-01 22:46:59 +0000:<br>
> Hi Doug,<br>
><br>
> Thanks for letting us know. Here's what we're intending...<br>
> - We'd like to release the server code for Mitaka.<br>
> - We release the client to Pypi, so that's already taken care of.<br>
> - We haven't moved our docs off of readthedocs yet, so we're taking care of<br>
> that as well.<br>
><br>
> I gave a +1 to your patch for adding openstack-server-release-jobs to zuul.<br>
> I also pushed a congress-only patch for the same, thinking that's probably<br>
> what you actually wanted us to do.<br>
> <a href="https://review.openstack.org/#/c/300682/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/300682/</a><br>
<br>
Now that the jobs are in place, we should tag new release candidates<br>
using new versions and the same SHAs as the last candidate to get the<br>
artifacts built properly. You can submit the request for that using the<br>
releases repo, or you can tag yourself and submit the info after the<br>
fact. We will decide what to do about the old artifacts you have on<br>
launchpad separately.<br>
<br>
><br>
> I gave a -1 to your patch that removes all the Congress deliverables from<br>
> openstack/releases, thinking that we can have this sorted out quickly. The<br>
> job we're missing just produces a tarball and uploads it, right? We've<br>
> been manually doing releases up to this point, which is why we didn't have<br>
> the job in place.<br>
> <a href="https://review.openstack.org/300644" rel="noreferrer" target="_blank">https://review.openstack.org/300644</a><br>
><br>
> I didn't touch your change on the artifact-link-mode, since it seems like a<br>
> short-term solution that may go in before we get everything sorted.<br>
> <a href="https://review.openstack.org/300457" rel="noreferrer" target="_blank">https://review.openstack.org/300457</a><br>
<br>
Yes, we'll merge that as a short-term fix until we have the rest of it<br>
worked out.<br>
<br>
Doug<br>
<br>
><br>
> Tim<br>
><br>
> On Fri, Apr 1, 2016 at 1:23 PM Doug Hellmann <<a href="mailto:doug@doughellmann.com" target="_blank">doug@doughellmann.com</a>> wrote:<br>
><br>
> > Congress team,<br>
> ><br>
> > We noticed in our audit of the links on<br>
> > <a href="http://releases.openstack.org/mitaka/index.html" rel="noreferrer" target="_blank">http://releases.openstack.org/mitaka/index.html</a> that the links to<br>
> > the build artifacts for congress point to missing files. The<br>
> > repository doesn't seem to have any real build jobs configured in<br>
> > openstack-infra/project-config/zuul/layout.yaml, so it's not clear<br>
> > how tagging is producing a release for you.<br>
> ><br>
> > For now, we are disabling links to the artifacts for those repos<br>
> > via <a href="https://review.openstack.org/300457" rel="noreferrer" target="_blank">https://review.openstack.org/300457</a> but we're also planning to<br>
> > remove them from the official Mitaka page since there don't<br>
> > appear to be any actual related deliverables<br>
> > (<a href="https://review.openstack.org/300644" rel="noreferrer" target="_blank">https://review.openstack.org/300644</a>).<br>
> ><br>
> > It would be good to understand what your intent is for builds. Can<br>
> > you follow up here on this thread with some details?<br>
> ><br>
> > Thanks,<br>
> > Doug<br>
> ><br>
> > __________________________________________________________________________<br>
> > OpenStack Development Mailing List (not for usage questions)<br>
> > Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> ><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div></div></div>