Since there have been no further updates on this thread, I think we should
be good to cut the 1.19.0-incubating release.

The last big change that got merged was about the non-persistent topics.

I have one more PR that I'd like to include:
https://github.com/apache/incubator-pulsar/pull/514
(to have a flag that enable static linking, which is needed to create the
self-contained python client dist file)


After that, if there no objections, I'll start preparing the first
candidate package.

Matteo



--
Matteo Merli
<mme...@apache.org>

On Tue, Jul 25, 2017 at 9:41 AM, Matteo Merli <mme...@apache.org> wrote:

> On Mon, Jul 24, 2017 at 3:20 PM, Dave Fisher <dave2w...@comcast.net>
> wrote:
>
>> In item #3 of the release process two additional checks are needed to
>> help with voting.
>>
>> (a) The output for the RAT report needs to be examined to make sure that
>> all of the source has the proper headers. That any excluded files are
>> properly explained.
>>
>
> Sure, right now the RAT check is performed in every CI build (to make sure
> that Pull Requests are validated before getting merged). In any case, the
> -src.tar.gz package content would be slightly different from the git
> repository workdir, so it's a good idea to check it at the release.
>
> I have updated the step #3 to add the "mvn apache-rat:check" verification.
> As for the excluded files, the current list is in:
> https://github.com/apache/incubator-pulsar/blob/master/pom.xml#L635
>
>
>> (b) The two release artifacts need to have hashes generated so that users
>> can be sure that they downloaded the genuine package. I believe that MD5
>> and SHA256 are now typical ...
>>
>
> Yes, I have included that in the following step: "4. Sign and stage the
> artifacts"
> There is a small shell script that creates checksum and sign all the
> tar.gz files.
>
> https://github.com/apache/incubator-pulsar/blob/master/src/sign-release.sh
>
>

Reply via email to