Hi Yishay, I am working on the existing steps as we speak ... I'm talking about after that. I want to learn what in general the hard requirements are and start a discussion on them because currently a lot of "steps" are implemented in order to achieve something. I want to learn not what is currently being done, but what this step is trying to achieve. Cause perhaps there are multiple ways to achieve the same goal.
Chris Am 21.03.20, 12:12 schrieb "Yishay Weiss" <[email protected]>: I would add being able to work on it incrementally. That is, a failure in one step does not mean previous steps are thrown away. Not sure how feasible that is, but I think it would be nice to have. From: Christofer Dutz<mailto:[email protected]> Sent: Saturday, March 21, 2020 11:20 AM To: [email protected]<mailto:[email protected]> Subject: Requirements for Releases Hi all, I would like to use this thread to collect some requirements for the release process. Also would I like to ask you not to formulate things like “The release artifacts must be built with X” but rather “The release artifacts should be usable by X” cause that’s what really matters. I hope you get what I mean. So far I have this: * The release artifacts should be usable by Maven * The release artifacts should be usable by Ant * The release should include tests, which ensure the correct function of the royale-maven-plugin * The release should include tests which ensure the correct function of the Ant targets * It should be possible to verify a release by comparing it’s binary artifacts for equality (reproducible builds) * It should be ensured a release candidate builds correctly with Ant and with Maven * The release process should ideally work on any machine Did I miss something? Chris
