> On Mar 29, 2022, at 10:51 AM, sebb <[email protected]> wrote:
> 
> On Tue, 29 Mar 2022 at 15:27, Rob Tompkins <[email protected] 
> <mailto:[email protected]>> wrote:
>> 
>> I wonder if the python script will be effective in doing the migration 
>> properly. I’ll try to carve some time out to help here.
> 
> In the case of Commons, most of the components have very similar
> needs, so one can probably just copy existing workflows from another
> component and adjust slightly.

With youi there….just thinking that it might not be exactly 1-to-1 such that a 
python script automating the migration would work.

-Rob

> 
>> -Rob
>> 
>>> On Mar 29, 2022, at 10:19 AM, sebb <[email protected]> wrote:
>>> 
>>> On Tue, 29 Mar 2022 at 13:57, Matt Juntunen <[email protected]> 
>>> wrote:
>>>> 
>>>> Hi Sebb,
>>>> 
>>>> Yep, geometry is still using Travis. I've never used GitHub Actions so
>>>> I'm not sure what it's capable of. Are there any specific features it
>>>> provides that are driving the migration to it? Or is it more a matter
>>>> of community preference? Either way is fine, I'm just curious.
>>> 
>>> It looks like Infra may be intending to migrate projects:
>>> https://cwiki.apache.org/confluence/display/INFRA/Travis+to+GitHub+Actions+Migration
>>> 
>>>> Regards,
>>>> Matt J
>>>> 
>>>> On Tue, Mar 29, 2022 at 7:22 AM sebb <[email protected]> wrote:
>>>>> 
>>>>> It looks like there is a general move to switch from Travis to GitHub 
>>>>> Actions.
>>>>> AFAICT the following components are still using Travis:
>>>>> 
>>>>> geometry
>>>>> jelly
>>>>> jxpath
>>>>> math
>>>>> numbers
>>>>> rng
>>>>> weaver
>>>>> 
>>>>> Do we need to move these as well?
>>>>> 
>>>>> BTW, emails from GHA runs can now be directed to project mailing
>>>>> lists, which is great (*)
>>>>> See: https://s.apache.org/asfyaml-gha
>>>>> 
>>>>> e.g. update .asf.yaml to include:
>>>>> notifications:
>>>>> ...
>>>>> jobs: [email protected]
>>>>> 
>>>>> Sebb.
>>>>> (*) Travis always had this, but recently switched to a new email
>>>>> system which means all such mails have to be moderated.
>>>>> 
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: [email protected]
>>>>> For additional commands, e-mail: [email protected]
>>>>> 
>>>> 
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [email protected]
>>>> For additional commands, e-mail: [email protected]
>>>> 
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>> 
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected] 
>> <mailto:[email protected]>
>> For additional commands, e-mail: [email protected] 
>> <mailto:[email protected]>
>> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected] 
> <mailto:[email protected]>
> For additional commands, e-mail: [email protected] 
> <mailto:[email protected]>

Reply via email to