samza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: [VOTE] Release Apache Samza 0.7.0-incubating RC0
Date Sun, 29 Jun 2014 00:44:31 GMT
On 29 June 2014 01:02, Jakob Homan <jghoman@gmail.com> wrote:
> This is vote for Samza's 0.7.0 release.  The PPMC vote passed 6x+1 6
> (Martin, Jakob, Yan, Sriram, Zhijie, Garry):
> http://bit.ly/samza070releasevote
>
> The release candidate can be downloaded from here:
> http://people.apache.org/~martinkl/samza-0.7.0-rc0/

[The alternative is to use the dist/dev area at

https://dist.apache.org/repos/dist/release/incubator/samza

when that has been created.
This makes it easier to publish the files once the vote passes, as the
dev and release trees are in the same SVN repo.]

There's a problem with the NOTICE file in Git.

It includes the paragraph:

>>
This product includes software developed by The Apache Software
Foundation (http://www.apache.org/).
<<

This should be

>>
This product includes software developed at
The Apache Software Foundation (http://www.apache.org/).
<<

Note in particular that it is "developed AT" not "developed BY" -
which has a rather different meaning.

The LICENSE file includes references to several third party software items.
However, their version numbers are not specified.
Since the license may change between versions, it is important to
specify the version to which the specific license applies.

The LICENSE file also appears to contain several copies of some licences.
This is unnecessary and confusing.
Where there are several additional licenses apart from the AL2.0, it
is usually better to store the licences in separate files which are
referenced from the LICENSE file itself, for example:

This product includes Foo version 1.3.01 under the XYZ licence, see path/XYZ.txt
etc.

> The release candidate is signed with pgp key ED78F8F5352D8EDF, which is
> included in the repository's KEYS file:
> https://git-wip-us.apache.org/repos/asf?p=incubator-samza.git;a=blob_plain;f=KEYS;h=7c59d68a82a6b6172334725962583b2fa8071242;hb=HEAD

The KEYS file should be stored at the top level of the Samza directory
under dist/incubator on the ASF host.
It will be needed there for the download page.
This must link to the mirror system for the source, but sigs and
hashes must be linked from the ASF host (they are not replicated to
mirrors)

It looks like the directory has not yet been created.

This will obviously have to be done before a release can be made.

Also, the dist release area [2] needs to be created before any files
can be published (once the VOTE passes)

[2] https://dist.apache.org/repos/dist/release/incubator/samza

AFAIK, this will require a JIRA for INFRA

> and can also be found on keyservers:
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xED78F8F5352D8EDF
>
> The git tag is release-0.7.0-rc0 and signed with the same pgp key:
> https://git-wip-us.apache.org/repos/asf?p=incubator-samza.git;a=tag;h=refs/tags/release-0.7.0-rc0
>
> 155 issues were resolved for this release:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20AND%20fixVersion%20%3D%200.7.0%20AND%20status%20in%20(Resolved%2C%20Closed)
>
> Here's my +1 (binding)

Mime
View raw message