You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@taverna.apache.org by Stian Soiland-Reyes <st...@apache.org> on 2019/03/25 17:14:29 UTC
Taverna repository release plan
On Mon, 25 Mar 2019 17:03:44 +0000, Stian Soiland-Reyes <st...@apache.org> wrote:
> Three most important unfinished issues to address before graduating:
>
> 1. Re-engage PPMC members
> 2. Release IP-fixed repositories
Here are the repositories that need to be released and get through
incubator PMC before graduation now that we have fixed their IP issues:
https://github.com/apache/incubator-taverna-language
https://github.com/apache/incubator-taverna-osgi
https://github.com/apache/incubator-taverna-engine
https://github.com/apache/incubator-taverna-workbench
https://github.com/apache/incubator-taverna-workbench-common-activities/
https://github.com/apache/incubator-taverna-workbench-product
Presuambly IP-clean (initiated after incubation), but also nice to
release:
https://github.com/apache/incubator-taverna-mobile
https://github.com/apache/incubator-taverna-plugin-gis
https://github.com/apache/incubator-taverna-databundle-viewer
https://github.com/apache/incubator-taverna-maven-parent
I'm afraid that would be quite a bit of [VOTE]s, so better chunk them
together somewhat? Suggested order:
1) taverna-mobile (src only?)
2) taverna-maven-parent + taverna-language
3) taverna-osgi + taverna-engine
4) taverna-workbench*
5) taverna-plugin-gis, databundle-viewer (src only)
Any volunteers for Release Manager of any of those? I can do 2) and 4)
> ..
> How has the project developed since the last report?
>
> Previous IP/licensing issues now resolved.
> Pending release of updated git repositories.
Added:
Moved Git repositories to GitHub via GitBox
--
Stian Soiland-Reyes
https://orcid.org/0000-0001-9842-9718
RE: Taverna repository release plan
Posted by Ian Dunlop <ia...@gmail.com>.
Hello,
For the TavMob release I guess we have to:
Tag https://taverna.incubator.apache.org/community/releasing#tagging-and-next-snapshot-version eg 1.0-incubating-RC1
Sign the .tar.gz https://apache.org/dev/release-signing.html
Upload to dist https://taverna.incubator.apache.org/community/releasing#uploading-to-distapacheorg
Vote https://taverna.incubator.apache.org/community/releasing#voting
Cheers,
Ian
Sent from Mail for Windows 10
From: Ian Dunlop
Sent: 28 March 2019 11:36
To: dev@taverna.incubator.apache.org
Subject: RE: Taverna repository release plan
Hello,
I’ve started going through the release procedure for taverna-osgi using the guide at https://taverna.incubator.apache.org/community/releasing (it’s been a while!). I’m confused by what I need to do about apache-taverna-maven-parent since it seems to be depending on parent-4 which I don’t think has been released yet according to https://issues.apache.org/jira/plugins/servlet/project-config/TAVERNA/versions. Does this matter? Or does
“Remember that in OSGi, as long as we follow semantic versioning and don't break API compatibility, an upstream dependency can be updated without forcing an update release of its downstream users.”
get around this issue. Ie can I release taverna-osgi to depend on an unreleased version of taverna-parent?
Cheers,
Ian
Sent from Mail for Windows 10
From: Ian Dunlop
Sent: 28 March 2019 11:00
To: dev@taverna.incubator.apache.org
Subject: RE: Taverna repository release plan
Hello,
I’ve created a GitHub tag for TavMob https://github.com/apache/incubator-taverna-mobile/releases/tag/v1.0. I propose we use the source .tar.gz bundle for the release. Shall I proceed with this release or does someone else want to try it? Let me know ASAP (today if possible).
I will also attempt to release OSGI & engine. I’m going to assume that there is no new code to go in them since they have been quiet for a bit.
Cheers,
Ian
Sent from Mail for Windows 10
From: Sagar
Sent: 27 March 2019 12:36
To: dev@taverna.incubator.apache.org
Cc: Ian Dunlop
Subject: Re: Taverna repository release plan
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 <st...@apache.org> wrote:
On Tue, 26 Mar 2019 10:54:17 +0000, Ian Dunlop <ia...@gmail.com> 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.
RE: Taverna repository release plan
Posted by Ian Dunlop <ia...@gmail.com>.
Hello,
I’ve started going through the release procedure for taverna-osgi using the guide at https://taverna.incubator.apache.org/community/releasing (it’s been a while!). I’m confused by what I need to do about apache-taverna-maven-parent since it seems to be depending on parent-4 which I don’t think has been released yet according to https://issues.apache.org/jira/plugins/servlet/project-config/TAVERNA/versions. Does this matter? Or does
“Remember that in OSGi, as long as we follow semantic versioning and don't break API compatibility, an upstream dependency can be updated without forcing an update release of its downstream users.”
get around this issue. Ie can I release taverna-osgi to depend on an unreleased version of taverna-parent?
Cheers,
Ian
Sent from Mail for Windows 10
From: Ian Dunlop
Sent: 28 March 2019 11:00
To: dev@taverna.incubator.apache.org
Subject: RE: Taverna repository release plan
Hello,
I’ve created a GitHub tag for TavMob https://github.com/apache/incubator-taverna-mobile/releases/tag/v1.0. I propose we use the source .tar.gz bundle for the release. Shall I proceed with this release or does someone else want to try it? Let me know ASAP (today if possible).
I will also attempt to release OSGI & engine. I’m going to assume that there is no new code to go in them since they have been quiet for a bit.
Cheers,
Ian
Sent from Mail for Windows 10
From: Sagar
Sent: 27 March 2019 12:36
To: dev@taverna.incubator.apache.org
Cc: Ian Dunlop
Subject: Re: Taverna repository release plan
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 <st...@apache.org> wrote:
On Tue, 26 Mar 2019 10:54:17 +0000, Ian Dunlop <ia...@gmail.com> 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.
RE: Taverna repository release plan
Posted by Ian Dunlop <ia...@gmail.com>.
Hello,
I’ve created a GitHub tag for TavMob https://github.com/apache/incubator-taverna-mobile/releases/tag/v1.0. I propose we use the source .tar.gz bundle for the release. Shall I proceed with this release or does someone else want to try it? Let me know ASAP (today if possible).
I will also attempt to release OSGI & engine. I’m going to assume that there is no new code to go in them since they have been quiet for a bit.
Cheers,
Ian
Sent from Mail for Windows 10
From: Sagar
Sent: 27 March 2019 12:36
To: dev@taverna.incubator.apache.org
Cc: Ian Dunlop
Subject: Re: Taverna repository release plan
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 <st...@apache.org> wrote:
On Tue, 26 Mar 2019 10:54:17 +0000, Ian Dunlop <ia...@gmail.com> 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.
Re: Taverna repository release plan
Posted by Sagar <ku...@gmail.com>.
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 <st...@apache.org>
wrote:
> On Tue, 26 Mar 2019 10:54:17 +0000, Ian Dunlop <ia...@gmail.com>
> 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.
RE: Taverna repository release plan
Posted by Stian Soiland-Reyes <st...@apache.org>.
On Tue, 26 Mar 2019 10:54:17 +0000, Ian Dunlop <ia...@gmail.com> 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! :)
RE: Taverna repository release plan
Posted by Ian Dunlop <ia...@gmail.com>.
Hello,
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.
Are you suggestion that OSGi & engine are released together? Or in the same release vote anyway.
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.
Do we have a date in mind for all this or just ASAP.
Cheers,
Ian
Sent from Mail for Windows 10
From: Stian Soiland-Reyes
Sent: 25 March 2019 17:14
To: dev@taverna.incubator.apache.org
Subject: Taverna repository release plan
On Mon, 25 Mar 2019 17:03:44 +0000, Stian Soiland-Reyes <st...@apache.org> wrote:
> Three most important unfinished issues to address before graduating:
>
> 1. Re-engage PPMC members
> 2. Release IP-fixed repositories
Here are the repositories that need to be released and get through
incubator PMC before graduation now that we have fixed their IP issues:
https://github.com/apache/incubator-taverna-language
https://github.com/apache/incubator-taverna-osgi
https://github.com/apache/incubator-taverna-engine
https://github.com/apache/incubator-taverna-workbench
https://github.com/apache/incubator-taverna-workbench-common-activities/
https://github.com/apache/incubator-taverna-workbench-product
Presuambly IP-clean (initiated after incubation), but also nice to
release:
https://github.com/apache/incubator-taverna-mobile
https://github.com/apache/incubator-taverna-plugin-gis
https://github.com/apache/incubator-taverna-databundle-viewer
https://github.com/apache/incubator-taverna-maven-parent
I'm afraid that would be quite a bit of [VOTE]s, so better chunk them
together somewhat? Suggested order:
1) taverna-mobile (src only?)
2) taverna-maven-parent + taverna-language
3) taverna-osgi + taverna-engine
4) taverna-workbench*
5) taverna-plugin-gis, databundle-viewer (src only)
Any volunteers for Release Manager of any of those? I can do 2) and 4)
> ..
> How has the project developed since the last report?
>
> Previous IP/licensing issues now resolved.
> Pending release of updated git repositories.
Added:
Moved Git repositories to GitHub via GitBox
--
Stian Soiland-Reyes
https://orcid.org/0000-0001-9842-9718