<div dir="ltr">Thanks for the effort put into this! My 2 cents in case you overlooked it: jobs and nodepool scripts need to be checked as they depend on the sf repo; these changes might impact them. </div><div class="gmail_extra"> <div class="gmail_quote">On Tue, Apr 18, 2017 at 4:31 AM, Tristan Cacqueray <<a href="mailto:tdecacqu@redhat.com" target="_blank">tdecacqu@redhat.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On March 27, 2017 9:28 am, Tristan Cacqueray wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Hello folks, with the recent packaging effort, it seems like the main software-factory repository could be split further: * sf-docs for docs/ * sf-config for config/ * sf-release for upgrade/ * <a href="http://release.softwarefactory-project.io" rel="noreferrer" target="_blank">release.softwarefactory-project.io</a> (or github similar page) for the README * sf-ci for the rest What do you think? -Tristan </blockquote> </div></div> Hello folks, here is a follow-up on this new organisation: * Content imported I used git filter-branch to keep the history and took this opportunity to remove the jar files that was in the history. The sf-config now weigh 4MB instead of 24MB :) * sf-config This package respects linux directory hierarchy, the main differences are: - Only sfconfig.py is installed in PATH, the rests of the scripts are now located in /usr/share/sf-config/scripts - The rest of static files are installed in /usr/share/sf-config, for exampels ansible roles are no longer copied in /etc/ansible - Lastly, all the generated content now lives in /var/lib/software-factory. * sf-release This package only contains the yum.repos.d file and the /etc/sf-release. More work is required to include the upgrade.sh script and its playbook. * sf-ci With this new structure, I'd like to initiate this project with local host based testing (without the image and lxc stuff). This work can happens in parallel with the current workflow to ensure a smooth transition. The test playbook would looks like this (on any centos slave): yum install sf-release yum install sf-config sfconfig.py nosetests -sv tests/ The upgrade test would be written like this: yum install sf-release-${PREVIOUS_VER} yum install sf-config sfconfig.py yum update sf-release upgrade.sh nosetests -sv tests/ Hopefully this should cut down test time by half! * software-factory/software-factory change Now the tricky part is to avoid desynchronisation... Both sf-docs and sf-config are forked from 96d0771 (current HEAD), thus I'd like to fast-track: <a href="https://softwarefactory-project.io/r/7507" rel="noreferrer" target="_blank">https://softwarefactory-project.io/r/7507</a> : remove config/ from main repo <a href="https://softwarefactory-project.io/r/7465" rel="noreferrer" target="_blank">https://softwarefactory-project.io/r/7465</a> : remove docs/ from main repo Thanks in advance! -Tristan _______________________________________________ Softwarefactory-dev mailing list <a href="mailto:Softwarefactory-dev@redhat.com">Softwarefactory-dev@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/softwarefactory-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/softwarefactory-dev</a> </blockquote></div> </div>