I agree with James, a lot of work is pending and lot needs to be done.
However aslo-v3 does support syncing activity when a release is *explicitly
*published by the developer.
Is this something similar to what you are looking for?
Here is a demo of the same https://www.youtube.com/watch?v=XNount5
I disagree. None of the automation proposed, or attempted in the
past, has solved our _human_ problem of not testing and tagging an
activity release.
It is a human problem which needs a non-technical solution;
attentiveness and willingness to act.
It also won't be solved by GSoC or GCI, because
A common issue across many activities is that changes are often not
released to ASLO. This must be automated to ensure that the work of
developers is reaching the users
My suggestion is to have an automatic sync with GitHub and ASLO;
When a new release tag is set on GitHub,
- the activity should
3 matches
Mail list logo
