Hi,
I must report a “-1” (binding) …
but in my case the typedefs are building correctly. Unfortunately, the build
produces SNAPSHOT versions and relies on SNAPSHOT versions. We can’t publish
this to the Apache Release repo and not have these released to Maven-Central.
This is a major issue for me.
Another minor issue would be that I must disable the RAT checks for the falcon
build as the flex-typedefs package contains files without the correct license
headers (I am reporting a technical issue here). If the flex-typedefs directory
should be bundled inside the compiler bundle, then the compiler bundles maven
RAT exclusions should be adjusted to work in this scenario. Testing an Apache
projects Release Candidate with disabled RAT checks isn’t good.
Chris
Am 11.06.17, 09:26 schrieb "Harbs" <harbs.li...@gmail.com>:
+1
Package
https://dist.apache.org/repos/dist/dev/flex/falcon/0.8.0/rc1/apache-flex-falconjx-0.8.0-src.tar.gz
Java 1.8
OS: Mac OS X x86_64 10.10.5
Source kit signatures match: y
Source kit builds: y
README is ok: y
README_JX is ok: y
RELEASE_NOTES is ok: y
RELEASE_NOTES_JX is ok: y
NOTICE is ok: y
LICENSE is ok: y
No unapproved licenses or archives in source package: y
No unapproved binaries in source package: y
Package
https://dist.apache.org/repos/dist/dev/flex/falcon/0.8.0/rc1/binaries/apache-flex-falconjx-0.8.0-bin.tar.gz
Binary kit signatures match: y
NOTICE is ok: y
LICENSE is ok: y
No unapproved licenses or files in jars: y
No unapproved licenses or archives in binary package: y
No unapproved binaries in binary package: y
> On Jun 10, 2017, at 12:59 AM, Alex Harui <aha...@adobe.com.INVALID> wrote:
>
> Hi,
>
> This is vote for the 0.8.0 release of the FalconJX (and Falcon)
> compilers. There is no separate Falcon-only release package at
> this time. The only purpose of the FalconJX packages are to serve as
> upstream packages for the FlexJS release.
>
> The release candidate can be found here;
> https://dist.apache.org/repos/dist/dev/flex/falcon/0.8.0/rc1/
>
> Before voting please review the section, 'What are the ASF requirements on
> approving a release?', at:
> http://www.apache.org/dev/release.html#approving-a-release
>
> At a minimum you would be expected to check that:
> - MD5 and signed packages are correct
> - README, RELEASE_NOTES, NOTICE and LICENSE files are all fine
> - That the build script completes successfully
> - That you can compile using the results of building the source package
>
> The source package is set up the same way as the repo. This means that
> the results of the build are not the same as the binary package. The
> compiled source package can be used to build FlexJS apps via the command
> line and Ant, but not in Flash Builder or other IDEs. You can test the
> source
> package by building it, then pointing to it from the source package of the
> FlexJS release candidate and building the examples in the FlexJS package.
>
> The binary package is set up as an upstream package for the FlexJS
> release. The most convenient way to use the binary package is to install
> a FlexJS SDK via Ant or the Installer.
>
> Please vote to approve this release:
> +1 Approve the release
> -1 Veto the release (please provide specific comments to why)
>
> This vote will be open for 72 hours or until a result can be called.
>
> The vote passes if there is:
> - At least 3 +1 votes from the PMC
> - More positive votes than negative votes
>
> Remember that this is a 'beta-quality' release so there
> will be many bugs found. The goal is not to try to find and fix bugs
> in the RC, but to make sure we have the packaging right, and enough
> functionality that folks will have some success trying to use it.
>
> People who are not in PMC are also encouraged to test out the release and
> vote, although their votes will not be binding, they can influence how the
> PMC votes.
>
> When voting please indicate what OS, IDE, Flash Player version and AIR
> version you tested with.
>
> Please put all discussion about this release in the DISCUSSION thread not
> this VOTE thread.
>
> For your convenience there is an ant script that automates the common
> steps to validate a release. Instead of individually downloading the
> package and signature files, unzipping, etc, you can instead:
> 1) create an empty folder,
> 2) download into that folder this file:
>
https://dist.apache.org/repos/dist/dev/flex/falcon/0.8.0/rc1/ApproveFalcon.
> xml
> 3) run the script: ant -e -f ApproveFalcon.xml -Drelease.version=0.8.0
> -Drc=1
>
> You are not required to use this script, and more testing of the packages
> and build results are always encouraged.
>
> Thanks,
> Alex Harui
>
