gearpump-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kam Kasravi <kamkasr...@gmail.com>
Subject Re: prepping for staging and voting on candidate release
Date Thu, 16 Jun 2016 22:12:10 GMT
Thanks Andy, Karol

The release process also suggests Rat - http://creadur.apache.org/rat/ for
auditing / verifying licenses.
Karol your report has a lot of unrecognized dependencies that are apache
based (eg zookeeper).
I'll try running the sbt license report and rat and see what they generate.

Kam

On Tue, Jun 14, 2016 at 12:34 AM, Karol Brejna <karolbrejna@apache.org>
wrote:

>
> In our project I used maven licence plugin. I see there is something
> similar for sbt: https://github.com/sbt/sbt-license-report
>
> I never used it but it probably do fine for us.
>
> I opened a Jira ticket (https://issues.apache.org/jira/browse/GEARPUMP-157)
> to validate/update
> https://github.com/apache/incubator-gearpump/blob/master/LICENSE
>
> Regards,
> Karol
>
>
>
>
> wt., 14.06.2016 o 02:42 u┼╝ytkownik Andrew Purtell <apurtell@apache.org>
> napisał:
>
>> Sorry for the hold up Kam.
>>
>> You will want to look at http://www.apache.org/dev/release.html
>>
>> We will need especially close attention to the contents of the LICENSE and
>> NOTICE files when making the first release. That FAQ talks about them
>> starting here http://www.apache.org/dev/release.html#license . If you are
>> only releasing a source package it is pretty straightforward. The signed
>> source package is mandatory anyway. If you want to also release binary
>> convenience packages with bundled dependencies, the LICENSE and NOTICE
>> files for the binary packages must enumerate all non-ASF licenses of the
>> bundled dependencies. Over on HBase we ended up automating the generation
>> of LICENSE and NOTICE files using quite a bit of Maven hackery. Perhaps
>> you'll want to start with only making a source package.
>>
>>
>>
>>
>> On Wed, Jun 8, 2016 at 3:12 PM, Kam Kasravi <kamkasravi@gmail.com> wrote:
>>
>> > The release process I've been looking at is here -
>> > http://www.apache.org/dev/release-publishing.html and the maven
>> > publishing link within this document.
>> >
>> > On Wed, Jun 8, 2016 at 2:59 PM, Kam Kasravi <kamkasravi@gmail.com>
>> wrote:
>> >
>> >> Hi Andy
>> >>
>> >> I would like to begin staging for a candidate release and call for a
>> vote.
>> >> You had mentioned there were some notes/caveats on the release process
>> >> you could provide?
>> >>
>> >> Thanks
>> >> Kam
>> >>
>> >
>> >
>>
>>
>> --
>> Best regards,
>>
>>    - Andy
>>
>> Problems worthy of attack prove their worth by hitting back. - Piet Hein
>> (via Tom White)
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message