[Sugar-devel] Issue tracking on Github?

[Tony Anderson]

Sugar activities from the beginning identified versions by version 
number. For some activities we have tens of versions in ASLO. Switching 
version control from a version number to git branches may be 
non-trivial. It would certainly be helpful to view changes to activities 
over time.

I still believe it is far more important to have a link from the ASLO 
entry for an activity to its github repo than to include the link in 
activity.info.

Tony

On 05/17/2016 07:37 PM, Walter Bender wrote:
>
> On Tue, May 17, 2016 at 12:35 PM, Dave Crossland <dave at lab6.com 
> <mailto:dave at lab6.com>> wrote:
>
>
>     On 17 May 2016 at 09:46, Walter Bender <walter.bender at gmail.com
>     <mailto:walter.bender at gmail.com>> wrote:
>
>         we need to send out a clear description of what is expected of
>         App developers ("transfer" their repos to sugarlabs) and how
>         to manage issues once the switch-over has occurred.
>
>
>     https://wiki.sugarlabs.org/go/Infrastructure_Team/Migrating_Bugs_to_GitHub
>
>
> Great. Thx.
>
>
>
> -- 
> Walter Bender
> Sugar Labs
> http://www.sugarlabs.org
>
>
>
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20160518/4eb8e9fd/attachment-0001.html>