.. completed! Hi Turbine devs,
Find more details, how it was done here: https://issues.apache.org/jira/browse/TRB-102. Some lessons learned: - To get a site registered, the branch name has to be "asf-site" and the file .asf.yaml has to exist and the prop set like this (for us, using it just in plain mode): publish: whoami: asf-site As only one asf-site branch could exist in a single repository different sites could be deployed only by setting subsite to a different sub site before commit/push, e.g. subdir: turbine/development/turbine-5-1 or subdir: turbine You will not find a branch release-x-asf-site. - The first time INFRA (puppet infrastructure) registers an asf-site it is cloned - and all path content deleted! Only if it's found the second time it will just be a git pull. That erased any already registered Fulcrum modules, as I could get turbine-fulcrum-site only late by a INFRa ticket ( https://issues.apache.org/jira/browse/INFRA-22328). Some more infos: Find all registered sites here (search for turbine): https://infra-reports.apache.org/site-source/ Find all registered (Turbine) gitboxes here: https://gitbox.apache.org/repos/asf I created a convenience repo for all currently migrated Fulcrum components usning gitmodules: https://github.com/apache/turbine-fulcrum-build Some todos still remain: - Update more README stuff/docs - Not all old content is currently uploaded, some jakarta docs are missing, and may be some Fulcrum are still missing or has to be removed from the list of currently supported /released components .. - Add a build script to Jenkins, register hook.. .. Next steps: Release turbine-fulcrum-parent, then may (at last!) come turbine-core .. Have fun! Best regards, Georg
smime.p7s
Description: S/MIME Cryptographic Signature
