On Wed, Aug 28, 2019 at 9:17 AM Austin Macdonald
wrote:
> I suggest posting demos individually. This will be more searchable, better
> to link to, and easier to consume. The community update portion could also
> be uploaded separately. The downside of fully asynchronous demos is that we
> lose
Austin & anybody feeling the pain of random CI failures:
It looks like the repo:
http://apt.postgresql.org/pub/repos/apt/dists/xenial-pgdg/main/binary-i386/Packages
Is an upstream repo added by Travis because we consume "postgresql" via
"addons" in .travis.yml file:
On Wed, Aug 28, 2019 at 11:34 AM Tatiana Tereshchenko
wrote:
> Bump.
>
> Please provide feedback if you have any.
> I'll start working on the PR to make the suggested change this week
> otherwise.
>
> Thank you,
> Tanya
>
> On Mon, Aug 26, 2019 at 12:46 PM Tatiana Tereshchenko
> wrote:
>
>> In
Bump.
Please provide feedback if you have any.
I'll start working on the PR to make the suggested change this week
otherwise.
Thank you,
Tanya
On Mon, Aug 26, 2019 at 12:46 PM Tatiana Tereshchenko
wrote:
> In RPM plugin we have Modulemd content. It comes from metadata as one file
> and we
I suggest posting demos individually. This will be more searchable, better
to link to, and easier to consume. The community update portion could also
be uploaded separately. The downside of fully asynchronous demos is that we
lose the Q in real time, but we haven't gotten much traction there.
On
FYI, I merged this change just now. pulpcore is went to republish its
bindings, but Travis is having intermittent network errors. I'll monitor
[0] to ensure it's publish completes soon.
For each plugin, whenever you merge next it should pickup this change in
your bindings as well. You could also
