Hi all,

We will cancel the vote again due to found issues with the missing licenses in the LICENSE file and copyrights in the NOTICE file for the binary release. We will try to change them according to the links Justin send. If someone has found other pressing issues that would block the next vote please let us know.

Thanks,
Jonas

 On Tue, 6 Nov 2018 10:42:22 -0800
 Luciano Resende <luckbr1...@gmail.com> wrote:
On Tue, Nov 6, 2018 at 10:07 AM Julian Hyde <jh...@apache.org> wrote:

Luciano,

Do you have a link to guidelines for what to put into LICENSE and
NOTICE of binary artifacts? I think it would help these folks iterate
faster.

Justin had sent the policy on the vote thread [1] which links to the
policy [2] which shows an example similar to the one I sent [3]

[1] https://www.mail-archive.com/general@incubator.apache.org/msg65405.html [2] http://www.apache.org/legal/release-policy.html#distribute-other-artifacts
[3] https://svn.apache.org/repos/asf/httpd/httpd/trunk/LICENSE


By the way, your example is good, but it includes the JSON license
with the infamous "The Software shall be used for Good, not Evil"
clause. Because of that clause JSON is now category X - it is not
allowed in Apache projects.


The example I used is from a project that is currently at the attic,
so it might not reflect the license categories of today, but the
intention was mostly to demonstrate how to describe/list license to
all other artifacts (mostly jars) that get included on a binary
distribution. I have seen other projects doing a license file per jar
which I personally don't like but it is accepted by the IPMC.


Julian

On Tue, Nov 6, 2018 at 7:32 AM Luciano Resende <luckbr1...@gmail.com> wrote:
>
> -1
>
> For the binary release, you will need to have a more descriptive
> license that incorporates all dependencies being shipped with the
> distribution.
>
> Here is a good example:
> https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/distribution/all/src/main/release/bin/LICENSE
>
> You need to check what needs to be listed in the NOTICE file as well,
> from the dependencies.
>
> On Mon, Nov 5, 2018 at 7:37 AM Jonas Pfefferle <peppe...@japf.ch> wrote:
> >
> > Hi all,
> >
> >
> > We prepared a new release to address the issues found in rc3. This is a call > > for a vote on releasing Apache Crail 1.1-incubating, release candidate 4.
> > The following issues has been addressed:
> >
> > * Append filename in checksum files to allow checking checksums with
> > "sha512sum -c"
> > * Add instruction to README to generate/access documentation locally from
> > source
> > * Add LICENSE, NOTICE and DISCLAIMER file to binary tarball and jars
> > META-INF
> > * Add top level directory to binary tarball
> > * Minor fixes in the documentation
> >
> > The source and binary tarball, including signatures, digests, etc. can be
> > found at:
> > https://dist.apache.org/repos/dist/dev/incubator/crail/1.1-rc4/
> >
> > The commit to be voted upon:
> > https://git-wip-us.apache.org/repos/asf?p=incubator-crail.git;a=commit;h=f34314a49a0ca795d163988e56778641ca2c7a1d
> >
> > The Nexus Staging URL:
> > https://repository.apache.org/content/repositories/orgapachecrail-1003/
> >
> > Release artifacts are signed with the key AA557B11:
> > https://www.apache.org/dist/incubator/crail/KEYS
> >
> > For information about the contents of this release, see:
> >
> > https://git-wip-us.apache.org/repos/asf?p=incubator-crail.git;a=blob_plain;f=HISTORY.md;hb=f34314a49a0ca795d163988e56778641ca2c7a1d
> > or for better readability
> > https://github.com/apache/incubator-crail/blob/v1.1-rc4/HISTORY.md
> >
> > Please vote on releasing this package as Apache Crail 1.1-incubating
> >
> > The vote will be open for 72 hours.
> >
> > [ ] +1 Release this package as Apache Crail 1.1-incubating
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because ...
> >
> > Thanks,
> > Jonas
> >
> >
> >
>
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/


--
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/


Reply via email to