Re: [Sugar-devel] [IAEP] Testing of Activities

2017-04-19 Thread Tony Anderson
I really am a newbie to git, but as I understand it, the master branch should be the point of development. Publishing an activity to ASLO should be a branch tagged with the incremented version number. So, in general, the master branch != the branch of the latest release published to ASLO. As w

Re: [Sugar-devel] [IAEP] Testing of Activities

2017-04-19 Thread Tony Anderson
I believe the plan is that GitHub is the source repository for the activities and git is used to maintain version control. Activities are published to ASLO with the bundles built by setup.py. As in most uses of git, a new bundle requires the version number to be incremented with the correspondin

Re: [Sugar-devel] [IAEP] Testing of Activities

2017-04-19 Thread Tony Anderson
Hi Walter, Based on my understanding of the GitHub process, I posted issues documenting the problems. Tony On 04/20/2017 12:09 AM, Walter Bender wrote: In the meantime, it may make sense to walk through all of the repos in sugarlabs on GH and ensure that those with changes get updated versio

Re: [Sugar-devel] [IAEP] Testing of Activities

2017-04-19 Thread Walter Bender
On Wed, Apr 19, 2017 at 3:23 PM, D. Joe wrote: > > So, is the idea here to add new git tags, for example: > > https://github.com/sugarlabs/write-activity/releases > > to keep the tags in line with the value of activity_version as changed, > for instance, in > this commit: > > https://github.com

Re: [Sugar-devel] [IAEP] Testing of Activities

2017-04-19 Thread D. Joe
So, is the idea here to add new git tags, for example: https://github.com/sugarlabs/write-activity/releases to keep the tags in line with the value of activity_version as changed, for instance, in this commit: https://github.com/sugarlabs/write-activity/commit/b95f2901941c0cff871124e042c76

Re: [Sugar-devel] [IAEP] Testing of Activities

2017-04-19 Thread Walter Bender
In the meantime, it may make sense to walk through all of the repos in sugarlabs on GH and ensure that those with changes get updated version numbers, new .xo and .gtar files, and we update ASLO and downloads. It seems our only mechanism for doing this is manual at the moment. Tony, if you publish

Re: [Sugar-devel] [IAEP] Testing of Activities

2017-04-19 Thread Chris Leonard
On Wed, Apr 19, 2017 at 1:30 AM, Tony Anderson wrote: > I spent the last two plus days testing the 137 activities with repositories > in github/sugarlabs. Thank you for this effort, clearly additional follow up is required and I hope it occurs. > Localization also needs some attention. The setup