You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@streams.apache.org by Justin Mclean <jm...@apache.org> on 2020/04/12 02:26:55 UTC
Re: [VOTE] Release Apache Streams 0.6.1 (RC1)
Hi,
Congratulations on your release.
However, from a quick look, I can see this still needs a little work as:
- You're still including the incubator DISCLAIMER but are no longer an incubating project
- You have a large number of things in NOTICE that probably should not be there
- There seems to be a few things missing from LICENSE
- You mention LGPL/GPL licenses and are including that license text. From a quick look, all dependencies are dual licensed so you should select the more compatible license.
I'm happy to help you in fixing these issues up if you need.
Kind Regards,
Justin
Re: DISCLAIMER, LICENSE, NOTICE changes for apache-streams
Posted by "sblackmon@apache.org" <sb...@apache.org>.
After a few more iterations I think the new binary distribution LICENSE is ready.
https://github.com/apache/streams/pull/505
I would especially appreciate feedback from those on PMC who have dealt with LICENSE/NOTICE matters on other projects.
I will lazy consensus merge this in 72 hours.
On Jul 1, 2020, 1:15 PM -0500, sblackmon@apache.org <sb...@apache.org>, wrote:
> Hello team. After some delay I’ve got some follow-up on this:
>
> I have opened a PR for STREAMS-663: Fix DISCLAIMER that I believe removes final traces of incubating references.
> https://github.com/apache/streams/pull/504
>
> In looking into what may be missing from LICENSE, it’s not obvious to me what that would be. I’ve created STREAMS-664 to track this and commented there:
> https://issues.apache.org/jira/browse/STREAMS-664
>
> And also have created STREAMS-665 to track changes to NOTICE we may want to make prior to our first binary/bytecode release. I am looking into that now, examining what is and is not present in NOTICE for a handful of peer projects.
>
> Steve Blackmon
> On Apr 28, 2020, 5:38 PM -0500, sblackmon@apache.org <sb...@apache.org>, wrote:
> > Justin,
> >
> > Thanks for your comment and offer to help.
> >
> > We are very interested in cleaning these items up sufficiently to begin releasing a binary distribution. We’ve resolved to do so in past discussions but never quite got there.
> >
> > I volunteer to take a first pass through based on your comments and open pull request(s) to move us closer in the next week.
> >
> > sblackmon
> > On Apr 11, 2020, 9:26 PM -0500, Justin Mclean <jm...@apache.org>, wrote:
> > > Hi,
> > >
> > > Congratulations on your release.
> > >
> > > However, from a quick look, I can see this still needs a little work as:
> > > - You're still including the incubator DISCLAIMER but are no longer an incubating project
> > > - You have a large number of things in NOTICE that probably should not be there
> > > - There seems to be a few things missing from LICENSE
> > > - You mention LGPL/GPL licenses and are including that license text. From a quick look, all dependencies are dual licensed so you should select the more compatible license.
> > >
> > > I'm happy to help you in fixing these issues up if you need.
> > > Kind Regards,
> > > Justin
DISCLAIMER, LICENSE, NOTICE changes for apache-streams
Posted by "sblackmon@apache.org" <sb...@apache.org>.
Hello team. After some delay I’ve got some follow-up on this:
I have opened a PR for STREAMS-663: Fix DISCLAIMER that I believe removes final traces of incubating references.
https://github.com/apache/streams/pull/504
In looking into what may be missing from LICENSE, it’s not obvious to me what that would be. I’ve created STREAMS-664 to track this and commented there:
https://issues.apache.org/jira/browse/STREAMS-664
And also have created STREAMS-665 to track changes to NOTICE we may want to make prior to our first binary/bytecode release. I am looking into that now, examining what is and is not present in NOTICE for a handful of peer projects.
Steve Blackmon
On Apr 28, 2020, 5:38 PM -0500, sblackmon@apache.org <sb...@apache.org>, wrote:
> Justin,
>
> Thanks for your comment and offer to help.
>
> We are very interested in cleaning these items up sufficiently to begin releasing a binary distribution. We’ve resolved to do so in past discussions but never quite got there.
>
> I volunteer to take a first pass through based on your comments and open pull request(s) to move us closer in the next week.
>
> sblackmon
> On Apr 11, 2020, 9:26 PM -0500, Justin Mclean <jm...@apache.org>, wrote:
> > Hi,
> >
> > Congratulations on your release.
> >
> > However, from a quick look, I can see this still needs a little work as:
> > - You're still including the incubator DISCLAIMER but are no longer an incubating project
> > - You have a large number of things in NOTICE that probably should not be there
> > - There seems to be a few things missing from LICENSE
> > - You mention LGPL/GPL licenses and are including that license text. From a quick look, all dependencies are dual licensed so you should select the more compatible license.
> >
> > I'm happy to help you in fixing these issues up if you need.
> > Kind Regards,
> > Justin
Re: [VOTE] Release Apache Streams 0.6.1 (RC1)
Posted by "sblackmon@apache.org" <sb...@apache.org>.
Justin,
Thanks for your comment and offer to help.
We are very interested in cleaning these items up sufficiently to begin releasing a binary distribution. We’ve resolved to do so in past discussions but never quite got there.
I volunteer to take a first pass through based on your comments and open pull request(s) to move us closer in the next week.
sblackmon
On Apr 11, 2020, 9:26 PM -0500, Justin Mclean <jm...@apache.org>, wrote:
> Hi,
>
> Congratulations on your release.
>
> However, from a quick look, I can see this still needs a little work as:
> - You're still including the incubator DISCLAIMER but are no longer an incubating project
> - You have a large number of things in NOTICE that probably should not be there
> - There seems to be a few things missing from LICENSE
> - You mention LGPL/GPL licenses and are including that license text. From a quick look, all dependencies are dual licensed so you should select the more compatible license.
>
> I'm happy to help you in fixing these issues up if you need.
> Kind Regards,
> Justin