Hi, > I dont think it is a matter of PMC vs. non-PMC members. AFAIK, Windows > users need to use the Installer to test the SDKs with existing Flex > projects.
What the issue with the constructFlexForIDE.bat or makeApacheFlexforIDE.bat scripts? > What are you testing then? The release as defined by Apache. See http://www.apache.org/dev/release.html#what "The Apache Software Foundation produces open source software. All releases are in the form of the source materials needed to make changes to the software being released. In some cases, binary/bytecode packages are also produced as a convenience to users that might not have the appropriate tools to build a compiled version of the source." And also http://www.apache.org/dev/release.html#what-must-every-release-contain "Every ASF release must contain a source package, which must be sufficient for a user to build and test the release provided they have access to the appropriate platform and tools. The source package must be cryptographically signed by the Release Manager with a detached signature; and that package together with its signature must be tested prior to voting +1 for release." "It is also necessary for the PMC to ensure that the source package is sufficient to build any binary artifacts associated with the release." And also http://www.apache.org/dev/release.html#approving-a-release "Before voting +1 PMC members are required to download the signed source code package, compile it as provided, and test the resulting executable on their own platform, along with also verifying that the package meets the requirements of the ASF policy on releases." > I dont agree with your definition of what a binding vote means. You can disagree but I think Apache fairly clear on this (see above). Thanks, Justin
