Hello,
To make a good start on this could everyone have a quick read of the
LICENCE, NOTICE and README.md in
https://github.com/apache/incubator-taverna-mobile to make sure that
they make sense and comply with the Apache rules. Once we are happy I
can start the release process. Hopefully a little bit of pre-work will
help to reduce the number of times we go round the release process. Here
is some info about the process
https://www.apache.org/legal/release-policy.html
Cheers,
Ian
On 07/12/2017 15:05, Ian Dunlop wrote:
Hello,
I think we cannot release an apk on google play until the release
candidate code has been voted on by the rest of the project and (I
think) the incubator PMC.
Cheers,
Ian
On 06/12/2017 16:10, Sagar wrote:
Hello,
I also agree with the Ian.
I am building a release candidate APK then Ian can go ahead with the
release process.
And I will share all the private details with you on
[email protected].
Sorry for late reply.
Thanks
<https://mailtrack.io/> Sent with Mailtrack
<https://chrome.google.com/webstore/detail/mailtrack-for-gmail-inbox/ndnaehgpjlnokgebbaldlmgkapkpjkkb?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality>
On Wed, Dec 6, 2017 at 8:26 PM, Ian Dunlop <[email protected]> wrote:
Hello,
There is nothing blocking it except time and people. I think we should
just go for the tar-ball and then worry about the market place
after. I'm
happy to be release manager but I also don't want to end up being the
blocker due to time constraints. If we make the assumption that the
code as
in the repo is good to go then we can make a start at the release
process.
How much of the existing release process applies? Is it just a case of
tarring it up and pushing to the release repo?
Cheers,
Ian
On 06/12/2017 11:03, Stian Soiland-Reyes wrote:
Who is willing to be Release Manager?
What is blocking? What do people need help with?
Should we release just the source tar-ball right awawy and then
package
binary for Android Market "privately"?
