Hi,
>> Gates that do not leave verified +1 are called non-voting, so
>> logically gates that leaves verified +1 are called voting gates.
> +1
Eh, what I wanted to +1 was:
+1 to promote the check jobs on rpm-packaging from MOS and SUSE CI as
voting jobs.
Sorry for mixing up definitions and then
Hi,
2016-09-29 14:12 GMT+02:00 Haïkel :
> Gates that do not leave verified +1 are called non-voting, so
> logically gates that leaves verified +1 are called voting gates.
+1
Greetings,
Dirk
__
On 16-09-29 08:12 AM, Haïkel wrote:
2016-09-26 16:05 GMT+02:00 Anita Kuno :
On 16-09-26 07:48 AM, Haïkel wrote:
Hi,
following our discussions about 3rd party gates in RPM packaging project,
I suggest that we vote in order to promote the following gates as voting:
- MOS
2016-09-26 16:05 GMT+02:00 Anita Kuno :
> On 16-09-26 07:48 AM, Haïkel wrote:
>>
>> Hi,
>>
>> following our discussions about 3rd party gates in RPM packaging project,
>> I suggest that we vote in order to promote the following gates as voting:
>> - MOS CI
>> - SUSE CI
>>
>>
On 16-09-26 07:48 AM, Haïkel wrote:
Hi,
following our discussions about 3rd party gates in RPM packaging project,
I suggest that we vote in order to promote the following gates as voting:
- MOS CI
- SUSE CI
After promotion, all patchsets submitted will have to validate these gates
in order to
Hi,
Thank you for bringing this topic up!
+1 from me.
We will do our best to keep services up-and-running from MOS (Mirantis)
side.
On 09/26/2016 02:48 PM, Haïkel wrote:
> Hi,
>
> following our discussions about 3rd party gates in RPM packaging project,
> I suggest that we vote in order to
Hi,
following our discussions about 3rd party gates in RPM packaging project,
I suggest that we vote in order to promote the following gates as voting:
- MOS CI
- SUSE CI
After promotion, all patchsets submitted will have to validate these gates
in order to get merged. And gates maintainers