Agree with stain. We can release using Github.

I have a question regarding the release files, which files we need to
include in it?

On Wed, Mar 27, 2019 at 2:02 AM Stian Soiland-Reyes <[email protected]>
wrote:

> On Tue, 26 Mar 2019 10:54:17 +0000, Ian Dunlop <[email protected]>
> wrote:
> > I’m not quite sure what the release process for 1) ie Taverna Mobile
> > would be. Bundle up the source in a tgz? I have the feeling I
> > suggested something a while back. I’ll need to dig through some old
> > emails.
>
> I think that's as good as it will get, we can just tag a release
> candidate and then download the tar.gz from GitHub, that should exclude
> .git
>
>
> > Are you suggestion that OSGi & engine are released together? Or in the
> same release vote anyway.
>
> Yes, separate releases, just concurrent VOTEs.
>
>
> > If we can think of how to approach 1) then I can put it together. I’m
> > happy to try 3) as well which is probably a much easier process since
> > it is maven/java.Well, as easy as that process ever gets.
>
> At least it's the same process every time :)
>
> Thanks!
>
>
> > Do we have a date in mind for all this or just ASAP.
>
> ASAP -so we can graduate! :)
>


-- 

Warmest regards
Sagar
Software Developer
Lattice Innovations Pvt. Ltd.

Reply via email to