[Sugar-devel] [Systems] v4.activities.sugarlabs.org (ASLO-v4) is up!

Srevin Saju srevinsaju at sugarlabs.org
Thu Jan 21 03:28:00 EST 2021


And now, (Thanks bernie_!), we can use 
https://v4.activities.sugarlabs.org/services/update-aslo.php for 
supporting sugar's microformat update system as mentioned below:

>   * support Sugar's microformat software upgrade feature in My
>     Settings, (Sugar 0.116 is configured
>     in|data/org.sugarlabs.gschema.xml|to use the AsloUpdater
>     in|src/jarabe/model/update/aslo.py|which reaches out to a PHP
>     script|update-aslo.php|, and will instead be configured to
>     use|src/jarabe/model/update/microformat.py|),
>
On 1/21/21 10:03 AM, Srevin Saju wrote:
> Right. I will configure ASLO-v4 to email sugar-devel@ with release 
> notifications.
> Thanks to all developers, mentors who helped me out with this. Had a 
> great experience working with it!!!
>
> On 1/21/21 10:00 AM, James Cameron wrote:
>> Thanks, great work.  Merged 204.
>>
>> I've also updated Browse.
>>
>> https://github.com/sugarlabs/browse-activity/commit/de3c4800ec705e5543c6be2c4d4695255d6e5aac 
>>
>>
>> I would prefer new version notifications to go to
>> sugar-devel at lists.sugarlabs.org, as that's one place we've seen them
>> previously.  aslo at lists.sugarlabs.org was for handling by library
>> editors, but we don't have any active, and we don't have the same
>> process with v4.
>>
>> On Thu, Jan 21, 2021 at 09:16:47AM +0300, Srevin Saju wrote:
>>> G'day!
>>>
>>> ASLO-v4 is finally up at https://v4.activities.sugarlabs.org! ... 
>>> with only
>>> a few more minor tidying up, ASLO-v4 will be ready for production.
>>>
>>> Activity maintainers can now push their bundles to ASLO-v4 by 
>>> following the
>>> instructions on https://wiki.sugarlabs.org/go/Service/activities4 as 
>>> well
>>> as, that mentioned in https://github.com/sugarlabs/sugar-docs/pull/204.
>>> Please feel free to reach out, so that I can improve the existing
>>> documentation, or anything you think is too complex.
>>>
>>> Next steps:
>>>
>>>   * Connect services/update-aslo.php and deploy a flask server (I am
>>>     trying to get a hold of some more good apache knowledge)
>>>   * Sending "new version detected" emails to aslo at lists.sugarlabs.org,
>>>     or should we create a new mailing list?
>>>
>>> -- 
>>> Srevin Saju
>>> https://srevinsaju.me
>>>
>> pub   RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) 
>> <srevinsaju at sugarlabs.org>
>>> sub   RSA 4096/14479587 2020-05-19
>>>
>>
>>
>>
>>> _______________________________________________
>>> Systems mailing list
>>> Systems at lists.sugarlabs.org
>>> http://lists.sugarlabs.org/listinfo/systems
>>
>>
>> _______________________________________________
>> Sugar-devel mailing list
>> Sugar-devel at lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel

-- 
Srevin Saju
https://srevinsaju.me

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0x1007816766D390D7.asc
Type: application/pgp-keys
Size: 4849 bytes
Desc: not available
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20210121/6ab6613e/attachment-0001.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20210121/6ab6613e/attachment-0001.sig>


More information about the Sugar-devel mailing list