On 14 Aug, Javier Pena wrote:
> Two months after this e-mail, we're having the same situation.
Looking at the example patch you used before, (which hasn't merged yet)
I see this as a combination of factors:
On one side, the fact that we are launching jobs that would not be
affected by the patch.
- Original Message -
> Hi,
>
> Thanks for starting this thread and apologies for not replying sooner.
>
> TL;DR:
> By means of "integration" between the two teams, I see this mostly as:
> - Let's talk to each other more (specs, discussing what you need, etc)
> - Let's do this in the open
On 06 Mar, Gabriele Cerami wrote:
> https://trello.com/c/xuRVmCDr/622-setup-teardown-tooling-bastion-host
> So the question is: is the bastion host in scope, or we have something
> different in mind when we talked about it ?
> We also more or less agreed that the bastion host will be
Hi,
TripleO CI team had a design session yesterday on the tasks for the
current sprint, which is addressing infra.
There are some open questions left, because we had important roles in
the team unavailable, and because we had to create and reprioritize some
of the cards yesterday, due to design de
Hi,
we'd like to participate actively in cleaning up after ourselves the
images we upload at each tripleo promotion. We are planning to do so
also for the container images in dockerhub, so part of this process has
to be done anyway. (maybe we should also do it in rdoregistry)
Since our access to t
