On Thu, Feb 21, 2019 at 5:03 AM Laura Wright wrote:
> I think from a design perspective we should try to make the features and
> documentation pages look more different from one another so users are less
> likely to mistake the different types of docs for one another. We can
> definitely address
I think from a design perspective we should try to make the features and
documentation pages look more different from one another so users are less
likely to mistake the different types of docs for one another. We can
definitely address this more in the site redesign. I can come up with
further
Hi,
TL;DR: please don't direct users to feature pages -- direct them to
end-user documentation instead. And maintain content separation between
end-user documentation and technical docs like feature pages.
...
Lately we've cleaned up documentation on ovirt.org, and I wanted to share
some of my
Il giorno mer 20 feb 2019 alle ore 16:07 Guillaume Pavese <
guillaume.pav...@interactiv-group.com> ha scritto:
> I am on the Trello board, but I can not create cards
>
Sorry for that, try using
https://trello.com/invite/b/5ZNJgPC3/f1b1826ee4902f348c44607765a15099/ovirt-431-test-day-1
for joining
I am on the Trello board, but I can not create cards
Guillaume Pavese
Ingénieur Système et Réseau
Interactiv-Group
On Wed, Feb 20, 2019 at 10:05 PM Sandro Bonazzola
wrote:
>
>
> Il giorno mar 12 feb 2019 alle ore 10:49 Sandro Bonazzola <
> sbona...@redhat.com> ha scritto:
>
>> Hi,
>> We are
Il giorno mar 12 feb 2019 alle ore 10:49 Sandro Bonazzola <
sbona...@redhat.com> ha scritto:
> Hi,
> We are planning to release the first candidate of 4.3.1 on February
> 20th[1] and the final release on February 26th.
> Please join us testing this release candidate right after it will be
>
The oVirt Project is pleased to announce the availability of the oVirt
4.3.1 First Release Candidate, as of February 20th, 2019.
This update is a release candidate of the first in a series of
stabilization updates to the 4.3 series.
This is pre-release software. This pre-release should not to be
For building the centos/rhel images I'm using the information from this
document
https://docs.google.com/document/d/1fxXBcgHnQr3r2qrSzXiSlpNMMLWnbq899s8rUP38KHw/edit?usp=sharing
On Wed, Feb 20, 2019 at 11:29 AM Yedidyah Bar David wrote:
> On Tue, Feb 19, 2019 at 8:51 PM Anton Marchukov
>
Eyal Edri writes:
> On Mon, Feb 18, 2019 at 4:03 PM Milan Zamazal wrote:
>
>> Hi, unless there is still anything preventing to make Vdsm 4.3 branch,
>> I'm going to make the branch soon.
>>
>> I posted the following patches to be merged to master soon after the
>> branch is created:
>>
>> -
On Tue, Feb 19, 2019 at 8:51 PM Anton Marchukov wrote:
> I think having the new base image working confirms the assumption that the
> problem was related to some old selinux package.
>
How are the images built? I searched a bit and found [1]. Do we run it
manually? In jenkins? Elsewhere? Do we
On Tue, Feb 19, 2019 at 8:47 PM Martin Perina wrote:
>
>
> On Tue, 19 Feb 2019, 19:22 Eyal Edri
>>
>>
>> On Tue, Feb 19, 2019, 19:45 Galit Rosenthal >
>>> Hi
>>>
>>> U/S CQ master passed after the use of an updated image
>>>
>>
>> +1, glad to hear that.
>> are we going to apply also the other
On Tue, Feb 19, 2019 at 7:17 PM Eyal Edri wrote:
> did it pass CI?
>
Yes of course
>
> On Tue, Feb 19, 2019, 18:50 Tal Nisan
>>
>> ___
>> Devel mailing list -- devel@ovirt.org
>> To unsubscribe send an email to devel-le...@ovirt.org
>> Privacy
12 matches
Mail list logo
