chetanmeh commented on issue #11: Create the project structure to release based on versions URL: https://github.com/apache/incubator-openwhisk-release/issues/11#issuecomment-360036183 > how does Apache Sling tie independent module releases into one consistent project release? @michaelmarth In Sling each module is release independently and the resulting maven artifact is deployed in a staging repo which is then voted upon. Depending on project the vote step can be like one of the below ones 1. Sling - Committers then use a [script][1] which downloads the artifact from the staging repo and validates its integrity. 2. In Jackrabbit Oak we use a [different script][2] which does following. Also see [vote mail][3] 1. Download the staged source zip 2. Run mvn verify 3. Perform checksum There is also a separate starter module which lists all the released and supported modules and produces a single Sling app. This module is currently released annually. > Also, how are git hashes and semver numbers mapped? In Sling and Jackrabbit we rely on maven tooling to create respective tags in git/svn which match the release version. The verify script use the tag to checkout code and build it [1]: https://github.com/apache/sling-tooling-release/blob/master/check_staged_release.sh [2]: https://dist.apache.org/repos/dist/dev/jackrabbit/check-release.sh [3]: https://lists.apache.org/thread.html/073a9bce496813c5fd7b0b83775ca95ab2eed83b971a3bb22b16034f@%3Coak-dev.jackrabbit.apache.org%3E
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
