[OM Cooker] [om-qa] kahinah enhancements

Efrem Mc efremmc2 at gmail.com
Thu Dec 8 10:54:08 EST 2016


Hi all:

I am not sure we want to put the "axe" to Kahinah before adding this
functionality to ABF.

I recall back in Nov 2014 everyone agreed to move to Kahinah for
testing and voting.  I guess the workflow is not working.
We need to agree on the workflow and use it.  Otherwise, explore what
it takes to add "voting" if nothing else to ABF.
I am not that close to the process and need to be, since I do some
testing.  We should publish a general workflow to follow.

Regards,

Efrem Mc

Reference:

Stated back on 11-13-14: (I just cut and paste.. no edits...)

3. Policies on stabilizing other branches than cooker -

We recognize policy that is crutacl to OMV distribution consistencty between
cooker and other branches - all kind imporvements(commits) related for other
than cooker branches MUST not overrun cooker, unless exceptional cases that
must be discussed on TC.

Commiting FLOW: cooker (master branch) -> own testing -> backport to other
branches -> QA testing (kahinah) -> publishing to repository

On Thu, Dec 8, 2016 at 8:48 AM, Tomasz Gajc <tpgxyz at gmail.com> wrote:
> I'd go further, and id' suggest to kill kahiniah, because we agreed long
> time ago that ABF will be extended with voting functionality.
> So when kahinah is alive then ABF will never reach new functionalities.
>
> 2016-12-08 7:56 GMT+01:00 Crispin Boylan <cris at beebgames.com>:
>>
>> Hi all
>>
>> As no-one is really voting on updates for 3.0 it seems to have left
>> kahinah in a bit of a state.
>>
>>
>> There are loads of updates which have either been published or rejected in
>> abf but are languishing on kahinah making it difficult to see what really
>> needs to be tested.  Some (hopefully!) minor enhancements to kahinah could
>> really help this situation:
>>
>> * Allow the maintainer of an update to reject it entirely, this would
>> elimate dud/superseded updates where the only thing the maintainer can do is
>> downvote it.
>>
>> * Update the kahinah list with the actual state of the package (ie instead
>> of only looking at Complete or Testing Published, if the update is
>> 'Published' then move it to published in kahinah, likewise if it is
>> 'Rejected' on ABF then reject it in kahinah.
>>
>>
>> is any of this achievable relatively quickly?
>>
>>
>> thanks
>>
>> cris.
>>
>>
>>
>> _______________________________________________
>> OM-Cooker mailing list
>> OM-Cooker at ml.openmandriva.org
>> http://ml.openmandriva.org/mailman/listinfo/om-cooker_ml.openmandriva.org
>
>
>
> _______________________________________________
> OM-QA mailing list
> OM-QA at ml.openmandriva.org
> http://ml.openmandriva.org/mailman/listinfo/om-qa_ml.openmandriva.org
>



More information about the OM-Cooker mailing list