Great!
On Thu, Jun 30, 2016, 4:25 AM Stian Soiland-Reyes wrote:
> On 17 June 2016 at 14:26, Stian Soiland-Reyes wrote:
> > The Taverna PPMC has successfully voted for the source release of
> >
> > Apache Taverna Engine 3.1.0-incubating
> > Apache Taverna Common Activities 2.1.0-incubating
>
On 17 June 2016 at 14:26, Stian Soiland-Reyes wrote:
> The Taverna PPMC has successfully voted for the source release of
>
> Apache Taverna Engine 3.1.0-incubating
> Apache Taverna Common Activities 2.1.0-incubating
> Apache Taverna Command-line Tool 3.1.0-incubating
I'm happy to announce
On 29 June 2016 at 21:06, Josh Elser wrote:
> +1 (binding)
Thanks, Josh!
> - command-line's NOTICE has a vague reference as the other projects to
> "Copyright 2010-2014 University of Manchester, UK", but not explicitly what
> applies. Might that be clarified (if it's simple).
It's tricky to
+1 (binding)
* Built from source and ran tests
* xsums/sigs good
* KEYS is up to date
* DISCLAIMER is present
* L&N present in source release artifacts (and also in JARs where
applicable)
- command-line's NOTICE has a vague reference as the other projects
to "Copyright 2010-2014 University of
Hi, we have +2 already for the below Taverna release candidate (Thanks
Justin and Sergio!) - do we have any other IPMC volunteers..?
Thanks!
On 17 June 2016 at 14:26, Stian Soiland-Reyes wrote:
> The Taverna PPMC has successfully voted for the source release of
>
> Apache Taverna Engine 3.1.0-
Hi,
> This is how it was suggested to us by our mentors; but we're open for
> improvements
Not it any way an issue, it’s just a bit more verbose that notice NOTICE files
I’ve seen.
> But is "Public Domain" valid outside US? Should we append ASF headers
> on it? (That should be allowed if it's
On 20 June 2016 at 16:31, Donal Fellows
wrote:
>> But is "Public Domain" valid outside US? Should we append ASF headers
> on it? (That should be allowed if it's PD.. at least if that is done
> by an USAnian)
> It certainly isn't on some jurisdictions (Germany is the most notable one)
> but I wou
Stian Soiland-Reyes wrote:
> But is "Public Domain" valid outside US? Should we append ASF headers
on it? (That should be allowed if it's PD.. at least if that is done
by an USAnian)
It certainly isn't on some jurisdictions (Germany is the most notable one) but
I would expect any German court t
On 20 June 2016 at 12:24, Sergio Fernández wrote:
> +1 (binding)
Thanks! Much appreciated!
> Non-blocking details I noticed (should be fixed in the next releases):
> * The three artifacts are related with each other, so I'd include some
> extra build information about the order when each one ne
On 18 June 2016 at 01:50, Justin Mclean wrote:
> Hi,
>
> +1 (binding). Can you fix the LICENSE and NOTICE issues in the next release
> please.
Thank you - already fixed in master. Getting smarter every day..
> I can help by reviewing the release but I’m at my limit mentor wise sorry.
Always a
HI,
> I would think this means that the taverna-execution-hadoop.jar file
> (which is distributed in Maven Central) must include the full notice
> "somewhere”,
Yes, it's normally it in a header of a file somewhere in a source release.
That’s why it best to put it somewhere and add a pointer to i
On 20 June 2016 at 12:49, Justin Mclean wrote:
>> license text should go in the LICENSE files, while NOTICE should just
>> contain a brief enumeration with some details (file/s, copyright holder,
>> license name and original source) about the third-party source components
>> included.
>
> Agree bu
On Mon, Jun 20, 2016 at 1:49 PM, Justin Mclean
wrote:
>
> > license text should go in the LICENSE files, while NOTICE should just
> > contain a brief enumeration with some details (file/s, copyright holder,
> > license name and original source) about the third-party source components
> > included.
Hi,
> license text should go in the LICENSE files, while NOTICE should just
> contain a brief enumeration with some details (file/s, copyright holder,
> license name and original source) about the third-party source components
> included.
Agree but just to make clear NOTICE should usually not inc
+1 (binding)
So far I've checked: signatures and digests, source releases file layouts,
matched git tags and commit ids, incubator suffix and disclaimer, NOTICE
and LICENSE files, license headers, build sources in a clean environment
(Maven 3.3.9, OpenJDK 1.8.0_91 64-Bit, Debian amd64).
Non-block
Hi,
+1 (binding). Can you fix the LICENSE and NOTICE issues in the next release
please.
> Note that Taverna still suffers from not having enough active mentors
I can help by reviewing the release but I’m at my limit mentor wise sorry.
I checked:
- artefact names contain incubating
- signatures
The Taverna PPMC has successfully voted for the source release of
Apache Taverna Engine 3.1.0-incubating
Apache Taverna Common Activities 2.1.0-incubating
Apache Taverna Command-line Tool 3.1.0-incubating
This is the first major release of Apache Taverna, following two
library releases whi
17 matches
Mail list logo
