Hello

The vote passes with
8  +1 overall
  3 from PPMC
  2 from IPMC
  2 from community
0 <= 0

Thank you all.  Now forwarding the vote to the IPMC for their consideration.

Joe


On Wed, Mar 11, 2015 at 10:32 PM, Dan Bress <[email protected]> wrote:
> +1 (non binding)
>
> LICENSE and NOTICE file present in source root(LICENSE contains correct 
> references to new licenses aggregated in this release, like MIT License for 
> asciidoctor)
> There is a README
> Both MD5 and SHA1 hashes match zip hash
> Zip ASC is properly signed by Joe Witt
> built with check licenses.  0 unapproved licenses
> Application works as expected
>
> Medium issue(don't remember if this was an existing issue in 0.0.1):
> "help"->"Rest Api" link does not work at all
>
> Minor issues:
> a) The following processors to not have processor/HTML documentation
> ConvertCSVToAvro
> ConvertJSONToAvro
> StoreInKiteDataset
>
> b) I'm noticing some weird behavior when moving a self loop relationships.  
> Steps:
> 1) drag a processor onto the graph
> 2) drag a relationship from that processor to its self
> 3) click on the relationship and move the bottom yellow dot down and to the 
> right
> 4) click the blue dot(end) of the relationship and move it to the top left of 
> the processor, then back onto the processor from the top left.
> (at this point I would expect the processor to be outlined in green when the 
> mouse moves over it, this seems to work kind of sporadically for me)
>
> Dan Bress
> Software Engineer
> ONYX Consulting Services
>
> ________________________________________
> From: Joe Witt <[email protected]>
> Sent: Wednesday, March 11, 2015 5:16 PM
> To: [email protected]
> Subject: Re: [VOTE] Release Apache NiFi 0.0.2-incubating (RC1)
>
> Ryan,
>
> Unless there is objection I'll add to our RM steps/check-list the
> inclusion of the convenience binary artifacts in the dev/dist area.
> In the release vote we can add a statement to the effect that
>
> "For convenience purposes we have provided the binary distribution
> built from the source release candidate here : LINK"
>
> We don't in any way want to give the impression that the binary
> distribution is being voted upon.  It is not.  The only thing being
> voted upon is the source release.
>
> Thanks
> Joe
>
> On Wed, Mar 11, 2015 at 5:10 PM, Ryan Blue <[email protected]> wrote:
>> On 03/11/2015 11:32 AM, Ryan Blue wrote:
>>>
>>> +1 (non-binding)
>>>
>>> Checks:
>>> * Signature is valid
>>> * Checksums match
>>> * Build (mvn clean install) from source tarball succeeds
>>> * RAT checks pass (mvn apache-rat:check)
>>> * NOTICE and LICENSE look fine (not a thorough validation)
>>>
>>> One thing I'd fix for the next release is the exclusion of test
>>> resources from the RAT check. Wouldn't it be better to do that by file
>>> extension (e.g., **/*.json, **/*.avro) to avoid not checking files that
>>> could have license headers?
>>>
>>> rb
>>
>>
>> I just went to test out the release build locally, but I can't find the
>> usually nifi-assembly tarball. Is that not included in the RC for some
>> reason?
>>
>> I know convenience binaries aren't required to release -- a release could
>> just be the source tarball. But if you intend to publish convenience
>> binaries, I think they should be included in the release candidate for
>> verification and testing.
>>
>>
>> rb
>>
>>> On 03/09/2015 07:31 PM, Joe Witt wrote:
>>>>
>>>> Hello
>>>>
>>>> I am pleased to be calling this vote for the source release of Apache
>>>> NiFi
>>>> nifi-0.0.2-incubating (RC1).
>>>>
>>>> The source zip, including signatures, digests, etc. can be found at:
>>>> https://repository.apache.org/content/repositories/orgapachenifi-1023
>>>>
>>>> The specific URL of the source zip is here:
>>>>
>>>> https://repository.apache.org/service/local/repositories/orgapachenifi-1023/content/org/apache/nifi/nifi/0.0.2-incubating/nifi-0.0.2-incubating-source-release.zip
>>>>
>>>>
>>>> The Git tag is nifi-0.0.2-incubating-RC1
>>>> The Git commit ID is 22c6735126ed42dce33386e3ae31e0715d742c89
>>>>
>>>> https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;a=commit;h=22c6735126ed42dce33386e3ae31e0715d742c89
>>>>
>>>>
>>>> Checksums of nifi-0.0.2-incubating-source-release.zip:
>>>> MD5: 1d542bb7259732bdbb1837ffb9553180
>>>> SHA1: b8877d9d190745a30d094c0b03be77f485c289fb
>>>>
>>>> Release artifacts are signed with the following key:
>>>> https://people.apache.org/keys/committer/joewitt.asc
>>>>
>>>> KEYS file available here:
>>>> https://dist.apache.org/repos/dist/release/incubator/nifi/KEYS
>>>>
>>>> 66 issues were closed/resolved for this release:
>>>>
>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12329373
>>>>
>>>> * We need to review our adherence to semantic versioning principles
>>>> going forward.
>>>>
>>>> The vote will be open for 72 hours.
>>>> Please download the release candidate and evaluate the necessary items
>>>> including checking hashes, signatures, build from source, and test.
>>>> The please vote:
>>>>
>>>> [ ] +1 Release this package as nifi-0.0.1-incubating
>>>> [ ] +0 no opinion
>>>> [ ] -1 Do not release this package because because...
>>>>
>>>
>>>
>>
>>
>> --
>> Ryan Blue
>> Software Engineer
>> Cloudera, Inc.

Reply via email to