Hi,
Some month ago with nbm-maven-plugin I started to experiment ATR release system from Apache. It's possible now to populate data to ATR from github to prepopulate template and basic information for better sync as it appears here https://github.com/apache/netbeans-parent/blob/master/.asf.yaml AFAIK, this kind of metadata may serve as replacement of doap and add information in the "global" Apache. I would like to experiment with netbeans-parent first in an upcoming release to adjust what is missing/needed to have more simple release and more systematic way to proceed. In short put more info in asf.yml file for a bit more controlled release. Another issue that I want to tackle Trying to populate mandatory data is occurs that subproject need download page and home page to be valid. I think it's maybe something I forget for netbeans-parent :D. We currently use Jenkins to get master branch build site, zip it. A cron job on the vm scan for hourly jenkins jobs to unzip to proper place on the vm website. This is legacy from apidoc system that we generalise to all mini subproject. It could be possible to use on git repository : netbeans-parent the asf-site branch with subdir directive to put on push the site data somewhere in the netbeans.apache.org Example: whoami: asf-site subdir: tooling/netbeans-parent netbeans.apache.org/tooling/netbeans-parent should contain the netbeans-parent data. this could make all subproject "standalone" on their contribution to main website. Neil also speak on linking to actual release. Making hypothesis that asf-site is configured for netbeans-parent. We could alter Jenkins build to check for each tag (filtering for release) and build to be put in tag subfolder on asf-site branch Folder will look like netbeans-1/{site build from tag commit} netbeans-2/{site .} . master/{site} Maybe some manual htaccess to put what is current release is. Any inputs appreciated. Best regards Eric
