Also a +1 from me.  Everything panned out.

All the best,
Matt


On Thu, Mar 3, 2022 at 11:03 AM Hans Van Akelyen <[email protected]> wrote:

> Hi All,
>
> We are proud to announce a 1.2.0 release candidate, this release is mainly
> a quality release with bug fixes and improvements, though some new features
> have been added too:
> - An Avro encode transform has been added allowing you to create avro
> records that can then be consumed by other transforms, the most important
> one being the kafka producer
> - The kafka transforms now support schema registry
> - ARM64 docker images are now available for both our images
> - The Chinese translations have had a major cleanup
>
> More details on what has been done can be found in the release notes.
>
> Build instructions can be found in the README included.
>
> The tag to be voted on is 1.2.0-rc1 (commit 49fa4a1):
> https://github.com/apache/hop/tree/1.2.0-rc1
>
> The release files, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/hop/apache-hop-1.2.0-rc1/
>
> The SHA512 Checksum for these artifacts is:
> source:
>
> feb66e570240ad8330480879086f8e1120d3d3b0352a6b0ddfe88c694d9ba3d6b5d4edab66a2e98eb4bba2260e74c4217262c8b1cc2b343dd3216aa50aa466d2
> client:
>
> 8e24bdcb5c2f9856711fbb2ac7ef3fc1c8f2edb366093657b1d3d1723f8320da6cd63d7d9ed6ab6fdaaa055df38dda805d095a99821ee9165c26ab23860934d6
>
> Release artifacts are signed with the following key:
> https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x9a8a628dd4f4aa1e
>
> For more information about the contents of this release, see:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12324323&version=12351230
>
> Please vote on releasing this package as Apache Hop 1.2.0!
>
> The vote is open for 72 hours and passes if
> a majority of at least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Hop 1.2.0
> [ ] +0 No opinion
> [ ] -1 Do not release this package because ...
>
> Best Regards,
> Hans
>


-- 
Neo4j Chief Solutions Architect
*✉   *[email protected]

Reply via email to