Yea, I think if we do the source-only release of Taverna Mobile, then unless that release plugin that was mentioned works, then we can just do it manually as it's not Maven-based.
So you would have to do a clean checkout, tag, tar (come up with filename scheme), make sha1/md5/asc files, then upload to https://dist.apache.org/repos/dist/dev/incubator/taverna/ to vote on. So it sounds easy, but still quite a lot.. so good if we could get that release plugin working. On Thu, 7 Dec 2017 09:39:50 +0000, Andy Seaborne <[email protected]> wrote: > >> How much of the existing release process applies? Is it just a case of > >> tarring it up and pushing to the release repo? > > It is a standard release process. > > There needs to be a VOTE by project, then source code goes to > a.o/dist/incubator/taverna. > > For binaries, they do have to agree with the source, so they should be > built at the same time otherwise you may have to change the source when > something is discovered making/testing binaries. > > Andy > > https://taverna.incubator.apache.org/community/releasing > > On 06/12/17 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"? > >>> > >>> > >>> > >> > > > >
