Hi Dave, Thanks for doing this. Your analysis is correct, however, you don't have to worry about Royale-compiler for now unless you want to. We are not currently using the Royale-compiler scripts to create artifacts, only royale-asjs. As you guessed, changing only the develop branch in royale-asjs should be sufficient.
Thanks, -Alex From: Dave Fisher <[email protected]<mailto:[email protected]>> Reply-To: <[email protected]<mailto:[email protected]>> Date: Wednesday, March 21, 2018 at 7:03 AM To: <[email protected]<mailto:[email protected]>> Subject: Change Planning for correct sha512 checksum files Hi - I’ve done an analysis of the source code and build scripts for the proper change for sha512 checksums and extensions. * Changes appear to be limited to Royale-asjs and Royale-compiler. Is this correct? In asjs the extension is currently SHA-512 and in compiler it is still MD5. The result will be that all artifacts will have SHA-512 with an sha512 extension. * What branches should I change? Develop? * In asjs changes need to be made to build.xml, ApproveRoyale.xml, and releasecandidate.xml? * In compiler changes need to be made to build.xml and ApproveFalcon.xml? * In compiler no changes for dependencies are required in any of the download.xml at this time. Changes may be needed later should we upgrade an Apache dependency that will no longer have a MD5. Regards, Dave
