IF it helps, I just checked in the ant script I use to cover the points Justin listed. It is in the flex-utilites repo in the TourDeFlex folder and called ApproveTDF.xml.
Use the command line: ant -e -f ApproveTDF.xml -Drelease.version=1.1 -Drc=1 Please actually review the reports dumped to the console. No fair just hitting 'y' ;-) -Alex On 9/4/14 11:05 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: >Hi, > >> Maybe this is a bit stupid question but how should I check TourDeFlex? > >The usual process is: >- check hashes and signatures >- check LICENSE and NOTICE >- check README and RELEASE_NOTES >- check that all source files has Apache headers (with Apache rat) >- check there's no binary files (other than images, fonts etc) in the >source release (rat can also do some of this) >- check you can compile from source >- check that it works > >These links should help [1][2]. But there are other things you can check, >or even just check a sub set of above, it's really up to you. Nice to >list what you checked and what platform you were on when voting. Given >that a few examples have been fixed and there a few new features (listed >in the VOTE email) that would be a good place to start. > >BTW it takes about 20-25 minutes to compile the 300 odd examples. > >Only PMC votes are binding but votes from committers and users are >welcome and quite often very useful, plus you'll get added to the >CONTRIBUTORS file if you test it out and vote. > >Thanks, >Justin > >1. http://www.apache.org/dev/release.html#approving-a-release >2. http://incubator.apache.org/guides/releasemanagement.html#best-practice
