Re: TavMob source, binary or both

[Stian Soiland-Reyes]

I think this sounds like a good approach, Ian!

Generally it is simpler to do just a source release - if we are doing
a binary release we also need to have a complete LICENSE/NOTICE for
our bundled dependencies:
https://www.apache.org/dev/licensing-howto.html#binary


However you already did the external licenses here:
https://github.com/apache/incubator-taverna-mobile/blob/master/app/src/main/assets/licences.html


And so we should be able to refer to this in the binary distribution -
that's the file that can be viewed form within the app, right?
(This seem to be missing our own NOTICE and the complete text of
Apache LICENSE, is that added in somehow?)


Given that the work of dependency licenses is done I would vote for
TavMobile as a source+binary release.

It might be easiest to put the apk manually (or with a shell script)
inside a zip next to a LICENSE and NOTICE and a copy of that
licenses.html? Otherwise you have to install and run the app to view
its (shrink-wrap) license..

Signing of the apk with Google Play does not need to be part of the
release process, in particular if that might mean "distributing" the
apk to Google Play prematurely.


If it is too much work, let's do just a source release (as we did with
server/cmd line) avoid more delays. But then we should not put it in
Google Play as an official "Apache Taverna Mobile" release, just
personally add it as "Taverna Mobile".


On 15 January 2018 at 12:00, Ian Dunlop  wrote:
> Hello,
>
> I'm going to try a release of TavMob soon. I'm not sure whether this
> should just be of the source code or whether we need to include a binary
> apk file as well. We could include an apk that people can test on their
> phones without needing Android studio etc. What we will need to do after
> release is then to sign it with the appropriate key for release via
> google play.
>
> Cheers,
>
> Ian
>
>



-- 
Stian Soiland-Reyes
http://orcid.org/-0001-9842-9718

TavMob source, binary or both

[Ian Dunlop]

Hello,

I'm going to try a release of TavMob soon. I'm not sure whether this
should just be of the source code or whether we need to include a binary
apk file as well. We could include an apk that people can test on their
phones without needing Android studio etc. What we will need to do after
release is then to sign it with the appropriate key for release via
google play.

Cheers,

Ian




signature.asc
Description: OpenPGP digital signature